Include the "unsigned" attribute in snapshot #198
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change will not have any effect on Postgres, which does not support signed integer. Support for SQLite is limited to non-primary keys integers, as SQLite does not support integer unsigned primary keys. MySQL support unsigned for both integer primary keys and simple integer.
|
Great job! |
lorenzo
added a commit
that referenced
this pull request
Feb 9, 2016
Include the "unsigned" attribute in snapshot
|
I'm glad to see that codecov report works. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This change will not have any effect on Postgres, which does not support signed integer.
Support for SQLite is limited to non-primary keys integers, as SQLite does not support integer unsigned primary keys.
MySQL support unsigned for both integer primary keys and simple integer.
This explains the differences between the comparisons files for each db vendors.
Refs #197