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

fix 10.5 compatibility broken in MDEV-19940 #2

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

grooverdan
Copy link

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.

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
grooverdan added a commit to grooverdan/MySQLTuner-perl that referenced this pull request Feb 5, 2021
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.
@grooverdan
Copy link
Author

note I tried to use executable comment syntax to fix this however ran into MDEV-24795

@grooverdan
Copy link
Author

Reminder 🏓

@Niek
Copy link

Niek commented Sep 3, 2021

Ping @shinguz

@grooverdan
Copy link
Author

happy belated PR anniversary.

@hstream-coder
Copy link

thanks for the fix <3

@mika
Copy link

mika commented Jul 12, 2023

@grooverdan thanks also from my side for the fix, this is required for MariaDB usage on Debian/bullseye and your PR works as expected ❤️

@Safranil
Copy link

Thanks for your PR, this solved an error while installing the sys database on MariaDB 10.5 on Debian 11.

@RealBrandon
Copy link

Thank you so much. This solved my problem while installing sys database on MariaDB 10.5.19 on Debian 11.

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

Successfully merging this pull request may close these issues.

6 participants