Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade the default version of MariaDB to a maintained version #25

Open
tormi opened this issue Aug 2, 2023 · 5 comments · May be fixed by #26
Open

Upgrade the default version of MariaDB to a maintained version #25

tormi opened this issue Aug 2, 2023 · 5 comments · May be fixed by #26

Comments

@tormi
Copy link

tormi commented Aug 2, 2023

MariaDB v10.3 is currently the default version for Lando, but is no longer maintained according to https://mariadb.org/download/#release-schedule:

The current maintained versions are: 10.4, 10.5, 10.6, 10.11 (maintained for 5 years), 10.9, 10.10, 11.0, 11.1 (maintained for one year).

@tormi tormi changed the title MariaDB v10.3 is not maintained anymore Upgrade the default version of MariaDB to a maintained version Aug 2, 2023
tormi added a commit to tormi/mariadb that referenced this issue Aug 2, 2023
tormi added a commit to tormi/mariadb that referenced this issue Aug 2, 2023
@tormi
Copy link
Author

tormi commented Dec 13, 2023

Also, sql_mode needs to be changed when switching from MariaDB 10.3 > 10.6. Otherwise it gives the following warning:

WARNING: Forcing protocol to TCP due to option specification. Please explicitly state intended protocol.

@tormi
Copy link
Author

tormi commented Feb 26, 2024

This is the current MariaDB EOL owerview:
Screenshot 2024-02-26 at 16 43 18

@onacymiketta
Copy link

Also, sql_mode needs to be changed when switching from MariaDB 10.3 > 10.6. Otherwise it gives the following warning:

WARNING: Forcing protocol to TCP due to option specification. Please explicitly state intended protocol.

Which sql_mode did you have to switch to?

@reynoldsalec
Copy link
Member

Ok, I've confirmed that the upgrade pathway from 10.3 -> 10.6 has an issue introduce in 10.5 around log entries: https://bbs.archlinux.org/viewtopic.php?id=259364. That error has come up several times in Lando issues, so I know it's legit. People have gotten around it by destroying their DBs, but it would be nice to figure out a way to more smoothly handle this.

@reynoldsalec
Copy link
Member

@pirog is suggesting that, due to the upgrade issues, probably our best solution for right now is to remove 10.3 from the legacy versions list so people don't get a warning, and keep the default until we have the Lando v4 API version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants