fix(postgres): Fix UNIQUE consuming tokens #3775
Merged
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 #3774
Currently
_parse_unique()
attempts to parse MySQL'sUNIQUE
constraint (#1708), which is parsed as:However, Postgres's
UNIQUE
(syntax below) does not seem to define<key>
so it must not preemptively consume an id_var for it:For this reason, this PR:
[<key>]
parsing in PostgresNOT NULLS DISTINCT
as a low-lift addition to increase DDL coverageDocs
Postgres UNIQUE | Postgres DEFAULT | MySQL UNIQUE