Fix inconsistent use of integer and bigInteger on MariaDB 10.3 #509
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.
Changes to support bigInteger wasn't done in full. It may be working for some database servers, but MariaDB 10.3 is not accepting to have a bigInteger increments column being referenced as integer on foreign keys.
To make it a little less verbose and easier to add on new migrations, I also created two new helper functions:
twillIncrementsMethod()
andtwillIntegerMethod()
.This is a broader fix than #502.