You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Constraints (initially CHECK and FOREIGN KEY) should be represented in pg-roll's internal schema representation.
Also, UNIQUE constraints should be part of the internal schema representation too.
Having constraints represented in the internal schema would enable:
Better validation of operations involving constraints:
Ensure that a constraint of the same name does not exist when adding a new constraint.
Ensure that the constraint exists when dropping a constraint.
Not having to specify the name of the column on which the constraint is defined when dropping a constraint (and the confusion that occurs when the wrong column is specified)
The content you are editing has changed. Please copy your edits and refresh the page.
…#242)
Add knowledge of `UNIQUE` constraints defined on a table to `pgroll`'s
internal schema representation.
`UNIQUE` constraints were already present as indexes, but this PR adds
them as their own top-level field in the `Table` schema and includes
information about the columns involved in the constraint.
Part of #105
…aint operation (#252)
Add extra validation to the drop constraint operation to ensure that the
constraint to be dropped actually exists on the table. Validation fails
if the constraint does not exist.
This is possible now that all supported constraints (`CHECK`, `UNIQUE`
and `FOREIGN KEY`) are part of the internal schema representation.
Part of #105
Constraints (initially
CHECK
andFOREIGN KEY
) should be represented inpg-roll
's internal schema representation.Also,
UNIQUE
constraints should be part of the internal schema representation too.Having constraints represented in the internal schema would enable:
Tasks
The text was updated successfully, but these errors were encountered: