mysql: do not use SERIAL alias in goose_db_version table creation #816
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.
We are using
goose
to run migrations on Vitess with MySQL setup. Unfortunately, Vitess does not supportSERIAL
keyword. Right now our work-around is to creategoose_db_version
table manually without usingSERIAL
keyword. We can solve this problem by NOT usingSERIAL
keyword and explicitly define the type of the column.This change is backwards-compatible
As stated in the MySQL documentation:
After table is created with
SERIAL
keyword, it automatically resolves tobigint(20) unsigned NOT NULL AUTO_INCREMENT
: