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 table name to text of validation contraint error message, to help identify error context [CORE4252] #4576
Comments
Modified by: Maxim Kuzmin (cybermax)priority: Major [ 3 ] => Trivial [ 5 ] |
Modified by: Sean Leyne (seanleyne)summary: Specify the name of the table, if an exception occurs when insert => Add table name to text of validation contraint error message |
Modified by: Sean Leyne (seanleyne)summary: Add table name to text of validation contraint error message => Add table name to text of validation contraint error message, to help identify error context |
Modified by: @asfernandes |
Commented by: @hvlad Error message now includes table name. |
Modified by: @hvladstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5.3 [ 10461 ] Fix Version: 3.0 Beta 1 [ 10332 ] assignee: Vlad Khorsun [ hvlad ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: Done successfully Test Details: TODO: add statements of other kind that violates not only not-null definition (PK/UK/FK/CHECK, domain boundaries ?) |
Submitted by: Maxim Kuzmin (cybermax)
Is duplicated by CORE4368
Is related to QA620
When occurs exception in INSERT, FB show info, like this:
The insert failed because a column definition includes validation constraints.
validation error for column ID_WRIT_OF_EXEC, value "*** null ***".
But if exception occurs in EXECUTE BLOCK or in program, sometimes impossible, looking at the name of the field, to determine the name of the table. Which complicates the correction of an error in database/program.
Commits: b826331 c0ac8b6 a736229 FirebirdSQL/fbt-repository@8f94aa3 FirebirdSQL/fbt-repository@511d4bc FirebirdSQL/fbt-repository@0c334b5
====== Test Details ======
TODO: add statements of other kind that violates not only not-null definition (PK/UK/FK/CHECK, domain boundaries ?)
The text was updated successfully, but these errors were encountered: