I see this notice in n8n worker:
Support for MySQL/MariaDB has been deprecated and will be removed with an upcoming version of n8n. Please migrate to PostgreSQL.
So, could I use n8n with MySQL in next version?
I see this notice in n8n worker:
Support for MySQL/MariaDB has been deprecated and will be removed with an upcoming version of n8n. Please migrate to PostgreSQL.
So, could I use n8n with MySQL in next version?
Hi @cmdntd987
Here they have mentioned this.
In the upcoming version the support for MySQL and MariaDB will be removed I guess. As long as you stay in the older version of n8n you can still use it. But the latest version you have to use Postgres.
Please help, I have default n8n caddy docker-compose file with SQLite, how can I change it to Postgres?
version: "3.7"
services:
caddy:
image: caddy:latest
restart: unless-stopped
ports:
- "80:80"
- "443:443"
volumes:
- ${DATA_FOLDER}/caddy_data:/data
- ${DATA_FOLDER}/caddy_config:/config
- ${DATA_FOLDER}/caddy_config/Caddyfile:/etc/caddy/Caddyfile
n8n:
image: n8nio/n8n
restart: always
ports:
- 5678:5678
environment:
- N8N_BASIC_AUTH_ACTIVE=true
- N8N_BASIC_AUTH_USER
- N8N_BASIC_AUTH_PASSWORD
- N8N_HOST=${SUBDOMAIN}.${DOMAIN_NAME}
- N8N_PORT=5678
- N8N_PROTOCOL=https
- NODE_ENV=production
- WEBHOOK_URL=https://${SUBDOMAIN}.${DOMAIN_NAME}/
- GENERIC_TIMEZONE=${GENERIC_TIMEZONE}
volumes:
- ${DATA_FOLDER}/local_files:/files
- ${DATA_FOLDER}/.n8n:/home/node/.n8n
volumes:
caddy_data:
external: true
caddy_config:```
How about SQLite? I guess SQLite will be slower than MySQL.
Do you have any request between Postgres or SQLite?
Why we must remove MySQL?
How it looks right now will MySQL initially still be supported, but it could then be removed any time afterwards. So official support goes away.
We do not have to remove it. But the reason why we do it, is that percentage wise, not many people are using it right now. At the same time does it cause a lot of work for our team with migrations that have to be written, tests that have to constantly be run with it (is a complexity multiplier), different versions that have to be supported, additional support requests, and so on. Time we can then invest into something else that provides more value to users.
Hello, can you create documention for those with mysql backend to migrate to postgres, can we use AWS RDS ?
As far as I know is it compatible with Maria DB and not Postgres, so no.
Ah yes. Documentation will obviously be provided in time.
Actually maybe it is actually compatible with Postgres. Do not know much about AWS services. That said, the answer is simple. If it is fully compatible with Postgres then yes, else no.
Have a postgres server running on RDS so should work fine.
Thanks a lot @BramKn !
Just saw that post with another user having problems: AWS RDS Postgres 15
Yeah I saw that topic. But that has nothing to do with postgres it self I think, as it will be a config issue or what ever. For me it just worked directly. Not sure on the version though.
Yep, works well with AWS RDS Postgresql 14.x
Hey all for clarification sake, it’s clear N8N is deprecating allowing use of MySQL for a backend storage system. Will N8N also deprecate the MySQL node in the frontend that is used in automations? Thanks
Welcome to the community @brandonbabb!
We will deprecate the use MySQL as a backend database for n8n. The MySQL node does not have anything to do with it. So it will definitely stay around.
Thanks so much!
You are welcome. Have fun!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.