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
Currently, only is_valid() is exposed, which just returns a bool.
It would be great to expose validate(), too, to get actual validation errors thrown (with information about why the validation is failing...).
The text was updated successfully, but these errors were encountered:
@wolfgangwalther @olirice I would like to contribute to the project, and take this issue. Can you take a look at PR #32 ?
Sorry, something went wrong.
I wonder if this would make it possible to return meaningful validation errors for CHECK constraints. For now, all we get for an invalid insert is:
ERROR: new row for relation "node" violates check constraint "node_column_check" DETAIL: Failing row contains (... some data ...).
resolved by #32
Successfully merging a pull request may close this issue.
Currently, only is_valid() is exposed, which just returns a bool.
It would be great to expose validate(), too, to get actual validation errors thrown (with information about why the validation is failing...).
The text was updated successfully, but these errors were encountered: