Fixes 5018 PostgreSql add Primary Key not nullable types #5020
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 #5018
π§βπ³ π§ Adds a mixin to the grammar to handle nullable types when adding a
PRIMARY KEY
withALTER TABLE
.PostgreSql Primary Key columns are NOT NULL
AlterTableAddConstraintMixin
This takes a lazyQuery as input, checks if the table constraint is a primary key, updates matching columns to not nullable, and returns a new lazyQuery with the transformed columns. This has the effect of propagating primary key nullability constraints to the columns when altering the table.
New
MigrationQueryTest
addedtested locally with https://github.com/griffio/sqldelight-postgres-01