Issue #236: Updates to handle stand-alone UNIQUE and UNIQUE KEY statements #237
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.
resolves #236
Updated parsing of
UNIQUE
andUNIQUE KEY
clauses and statements. Now when multiple columns are specified in aUNIQUE
clause/statement it will be treated as a compound UNIQUE statement and put in theconstraints
section of the parse dict. It also means that the individual columns will haveunique=False
since the individual column does not actually have a UNIQUE constraint. If I have done this correctly it will match the SQL spec more closely then before.