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
Currently, constraintViolation does not correcty parse the error message generated by Postgres when a check constraint on a domain is violated.
So, for instance, if I define a domain like this:
create domain foo as int check (value <> 42);
and then do something to violate the constraint, like so
select 42::foo;
then the error message generated by Postgres is: value for domain foo violates check constraint "foo_check" constraintViolation in that case returns Nothing because it expected the domain name to be surrounded by quotation marks.
The text was updated successfully, but these errors were encountered:
Currently,
constraintViolation
does not correcty parse the error message generated by Postgres when a check constraint on a domain is violated.So, for instance, if I define a domain like this:
and then do something to violate the constraint, like so
then the error message generated by Postgres is:
value for domain foo violates check constraint "foo_check"
constraintViolation
in that case returnsNothing
because it expected the domain name to be surrounded by quotation marks.The text was updated successfully, but these errors were encountered: