Fix SQL format so that it can be imported into MySQL #53
+18,660
−18,660
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 #52
Importing the .sql file into MySQL/MariaDB results in errors:
The issue seems to be with the table name and column names in the INSERT INTO statement. The column names shouldn't be prefixed with the table name (at least from MySQL's point of view).
Here is the corrected SQL statement using backticks to quote the reserved words:
Here is a
sed
command to do a bulk change to the SQL file:The other error that came up was that a semi-colon
;
is needed between eachinsert
statement.Here is another sed command to fix this:
After these changes the import into MariaDB/MySQL should work.