-
Notifications
You must be signed in to change notification settings - Fork 16
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
fix 10.5 compatibility broken in MDEV-19940 #2
base: master
Are you sure you want to change the base?
Conversation
varchar innodb information_schema columns that where effectively boolean got replaced by a int in MDEV-19940 in MariaDB-10.5.0. We use a MariaDB-10.2+ feature EXECUTE IMMEDIATE to form the VIEW expression correctly based on the version. Using EXECUTE IMMEDIATE we've effectively broken <=10.1 compatiblity which is now out of support from MariaDB upstream. closes FromDual#1
To fix 10.5 compatibility <10.2 compatibility was broken FromDual/mariadb-sys#2 Also only recommend this if the performance schema was compiled in this server version. A recompile the server recommendation would be a bit excessive.
note I tried to use executable comment syntax to fix this however ran into MDEV-24795 |
Reminder 🏓 |
Ping @shinguz |
happy belated PR anniversary. |
thanks for the fix <3 |
@grooverdan thanks also from my side for the fix, this is required for MariaDB usage on Debian/bullseye and your PR works as expected ❤️ |
Thanks for your PR, this solved an error while installing the |
Thank you so much. This solved my problem while installing |
varchar innodb information_schema columns that where effectively
boolean got replaced by a int in MDEV-19940 in MariaDB-10.5.0.
We use a MariaDB-10.2+ feature EXECUTE IMMEDIATE to form
the VIEW expression correctly based on the version.
Using EXECUTE IMMEDIATE we've effectively broken <=10.1 compatiblity
which is now out of support from MariaDB upstream.
closes #1
I hope this is acceptable @shinguz that provides effective compatibility for supported MariaDB versions.