fix: foreign key constraint "account_vipgroups" and "player_charms" #536
+5
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes two issues preventing the schema.sql file from importing correctly into MySQL.
Fix Foreign Key Constraint Error (Error Code: 6125):
The table
account_vipgrouplistattempts to create a Foreign Key referencing the id column ofaccount_vipgroups. However, theaccount_vipgroupstable was originally defined with a composite Primary Key (id, account_id). MySQL requires the referenced column in a foreign key constraint to be a unique key or the sole primary key. This caused the import to fail with Error 6125: Failed to add the foreign key constraint.Updated the
account_vipgroupstable definition to set the Primary Key strictly on the id column.Fix Syntax Error in player_charms:
Renamed the column to
tracker_list(standard snake_case) to resolve the syntax error and maintain naming consistency.