We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
type User { name: str; } type HasTwoOrFewerUsers { users: User; constraint expression on (count(.users) <= 2); }
This will work to create a migration, but then fail to apply:
InternalServerError: aggregate functions are not allowed in check constraints
If users is updated to be correctly multi then it properly fails at migration creation time:
users
multi
error: cannot use aggregate functions or operators in a non-aggregating constraint
Seems this should always be caught at creation time.
The text was updated successfully, but these errors were encountered:
I thought this was going to have been fixed by #7128, but it looks like we don't catch this at all, and the error comes from postgres.
The funny bit is that if users is actually a multi link, then we correctly reject it at migration create time!
Sorry, something went wrong.
dnwpark
No branches or pull requests
This will work to create a migration, but then fail to apply:
If
users
is updated to be correctlymulti
then it properly fails at migration creation time:Seems this should always be caught at creation time.
The text was updated successfully, but these errors were encountered: