-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add knowlege of constraints to internal schema representation #105
Comments
This was referenced Jan 17, 2024
andrew-farries
added a commit
that referenced
this issue
Jan 18, 2024
…#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
andrew-farries
added a commit
that referenced
this issue
Jan 26, 2024
…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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: