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
Internal migration scripts break MySQL 8.0, same issue as Vilma had previously at #569. This doesn't seem to fix my problems though, and I can only assume it's because of older MySQL version. MySQL 8.0 is the version that the majority uses, so I'd say it would be good to have compatibility with it, even if it's an older version. The error is exactly same as Vilma had, but I'm going to include it here as well:
Update ("up"):
--------------------------------------------------------------------------------
grate-internal\00_02_fix_version_table_casing_if_exists.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 (SELECT 1
FROM INFORMATION_SCHEMA.TABLES
' at line 1
To Reproduce
Have a MySQL server
Run grate -cs "XXX" --dbt "mariadb" --files "XXX"
Expected behavior
The script should not break the database migration.
Desktop (please complete the following information):
OS: Windows 11 Enterprise
Version: 1.8.0
Reference to the issue where this was "solved": #569
The text was updated successfully, but these errors were encountered:
Describe the bug
Internal migration scripts break MySQL 8.0, same issue as Vilma had previously at #569. This doesn't seem to fix my problems though, and I can only assume it's because of older MySQL version. MySQL 8.0 is the version that the majority uses, so I'd say it would be good to have compatibility with it, even if it's an older version. The error is exactly same as Vilma had, but I'm going to include it here as well:
To Reproduce
Have a MySQL server
Run
grate -cs "XXX" --dbt "mariadb" --files "XXX"
Expected behavior
The script should not break the database migration.
Desktop (please complete the following information):
Reference to the issue where this was "solved": #569
The text was updated successfully, but these errors were encountered: