-
-
Notifications
You must be signed in to change notification settings - Fork 173
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
Support Table CHECK
Constraints
#397
Comments
After some digging I found all three databases support CHECK constraint: |
I'll open this issue for contributions |
👋 Hey @billy1624! Happy to claim this if it's okay with you! |
Done! |
@nahuakang is there any news with this? |
@Razican Sorry I haven't had the time to got around to this issue. Are you interested in taking it? If so, please do :) I probably will only come back to this in 2-3 weeks earliest. |
Id be happy to give it a go :) |
@LemarAb hello! Any updates?) |
@ikrivosheev I made some progress but need some time to deeper understand how sea query translates the stmt into SQL. Will report soon. If necessary, can I ask you for help? |
Take your time! Yes, of course you can) |
Just to clarify: CHECK constraints on Columns are already supported through the extra() method. We want to add CHECK constraints for the whole table, right? As an example for Postgres:
We want to add support for the second constraint, the first is already supported, correct? |
@LemarAb we want to add the ability to add It will great if we can both) |
@ikrivosheev ok, so afaik we need to add check() to |
Discussed in #135
Originally posted by forrest-akin August 3, 2021
Currently, there's no way to specify table
CHECK
constraints inTableCreateStatement
s. Adding an.extra()
method similar toColumnDef
would probably be the easiest way to add support for this.The text was updated successfully, but these errors were encountered: