-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Fix database schema checker for MySQL 8 on staging branch #25658
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 database schema checker for MySQL 8 on staging branch #25658
Conversation
Fix case in column type check of database schema checker for MySQL 8.
|
@wilsonge Question: Shall I do a PR for 4.0-dev, too, or shall we wait until this is merged and then 3.9.11 will be merged to 4.0-dev? |
|
@MonkeyTrainer12 @breisig Please test. @ReLater Please spread in forum people shall test this PR. @mbabker Please review or at least notice desciption above about different behavior of "SHOW COLUMNS". |
|
Drone failure is javascript and so not related to this PR. |
Done. Let's see how lazy they are. And thank you for your efforts. I "bombed" my LInux with upgrading to MySQL 8 ;-) |
|
yes i had struggle too thanks god i bombed only a clone vm ;-) |
|
Sorry, had forgotten most important part. Fixed now. |
|
Grr, again mistake. Now it is really correct. |
|
Will test out the patch very soon. |
|
@breisig Did you already find time to test? If so, please mark your test result in the Joomla CMS issue tracker at https://issues.joomla.org/tracker/joomla-cms/25658. Just use the button "Test this", then select your test result and then submitt that with the corresponding button. |
|
I have tested this item ✅ successfully on 30cd879 This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/25658. |
|
@MonkeyTrainer12 @breisig One more tester only needed. Thanks @frostmakk for testing. |
|
@richard67 It looks like it works. |
|
@breisig please mark your test as successfully (how to: https://docs.joomla.org/Testing_Joomla!_patches#Recording_test_results) |
|
@MonkeyTrainer12 We still need one more tester because @breisig is either not willing or not able to mark his test result in the issue tracker like described e.g. here #25658 (comment) or here https://docs.joomla.org/Testing_Joomla!_patches#Recording_test_results . |
|
@breisig Thanks for your test, but please also mark your test result in the Joomla CMS issue tracker at https://issues.joomla.org/tracker/joomla-cms/25658. Just use the button "Test this", then select your test result and then submitt that with the corresponding button. As long as not marked, it is not counted, and as long as no 2 test, this PR will not be ready for merge. |
|
I have tested this item ✅ successfully on 30cd879 This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/25658. |
|
RTC This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/25658. |
|
Thanks! |
|
Thanks to all testers and to reporters for your patience, and thanks for merging of course. |
Pull Request for Issue #25452 for staging.
Summary of Changes
Fix case in column type check of database schema checker for MySQL 8.
When you enter e.g. the SQL statement
SHOW COLUMNS IN #__extensions WHERE field = 'enabled' AND type = 'TINYINT(3)';(using your db prefix of course and not
#__)in PhpMyAdmin on a Joomla 3.9.10 or staging database, you will get a result in MySQL 5.7 but not in MySQL 8.
But when you enter
SHOW COLUMNS IN #__extensions WHERE field = 'enabled' AND UPPER(type) = 'TINYINT(3)';you get a result on both MySQL versions.
In both cases type names are lowercase in the result, but on MySQL 8 the search seems to be case-sensitive, while it is case-insensitive e.g. on MySQL 5.7.
Testing Instructions
Result: See section "Actual result" below.
Result: See section "Expected result" below.
Expected result
No database errors.
Actual result
Database errors shown as described in issue #25452 , but when you check in the database and the schema update SQL mentioned in the error message, you will not see any reason because the data types match in all details those set by the schema update and also those in joomla.sql.
Documentation Changes Required
None.