Allow some named inline column constraints in CREATE TABLE
statements
#559
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.
Allow some named inline column constraints in
CREATE TABLE
statements.SQL like this can be converted to a pgroll
OpCreateTable
:The previous behaviour was to allow only the unnamed forms of these constraints:
Named inline column constraints remain unsupported for
DEFAULT
,NULL
,NOT NULL
,UNIQUE
andPRIMARY KEY
constraints and will fall back to a raw SQL operation.