You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
With 1.8.0 came a bug fix for schemas/tables with different casings (#557). However, the scripts use "ALTER TABLE IF EXISTS" syntax which doesn't seem to exist in MySQL, only in MariaDB. This breaks the database migration. The documentation says that grate supports MariaDB/MySQL, but in this specific case it doesn't. :)
To Reproduce
Have a MySQL server
Run grate -cs "XXX" --dbt "mariadb" --files "XXX"
Error occurs:
An error occurred: Migration failed due to the following errors:
Update ("up"):
--------------------------------------------------------------------------------
grate-internal\00_02_fix_version_table_casing.sql: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'IF EXISTS `grate_grateversion`
RENAME TO `grate_GrateVersion`' at line 1
Expected behavior
The script should not break the database migration.
Desktop (please complete the following information):
OS: Windows 11 Enterprise
Version: 23H2
The text was updated successfully, but these errors were encountered:
Describe the bug
With 1.8.0 came a bug fix for schemas/tables with different casings (#557). However, the scripts use "ALTER TABLE IF EXISTS" syntax which doesn't seem to exist in MySQL, only in MariaDB. This breaks the database migration. The documentation says that grate supports MariaDB/MySQL, but in this specific case it doesn't. :)
To Reproduce
Have a MySQL server
Run
grate -cs "XXX" --dbt "mariadb" --files "XXX"
Error occurs:
Expected behavior
The script should not break the database migration.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: