[DERBY-6773] Derby throws plain SQLIntegrityConstraintViolationException

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.10.2.0
• Fix Version/s: 10.12.1.2
• Component/s: JDBC
• Environment: Windows 7 x86_64, Java 1.6.0.45
• Issue & fix info: Newcomer
• External issue URL: https://hibernate.atlassian.net/browse/HHH-9516
• Assignee: Abhinav Gupta
• Reporter: Jochen Wiedmann
• Created: 22/Nov/14 15:31
• Updated: 09/Sep/16 09:51
• Resolved: 29/Oct/15 07:27

Description

If a unique constraint is violated by an insert statement, then Derby throws an SQLIntegrityConstraintViolationException. The error message contains, in particular, the constraint name and the table name.

To distinguish between cases with various constraints, Derby should instead throw a subclass of SQLIntegrityConstraintViolationException, with methods like getConstraintName(), and getTableName().

See also https://hibernate.atlassian.net/browse/HHH-9516.

Issue Links

• relates to: DERBY-6779 Provide subclass of SQLException for duplicate key insertions

Sub-Tasks

• Implement DerbySQLIntegrityConstraintViolationException class: Closed
• Implement MessageUtils class so client and server can share message argument encoding/decoding: Closed
• Change NetworkServer code to use new MessageUtils class: Closed
• Change Sqlca and SqlException in NetworkClient to call MessageUtils: Closed
• Change SQLExceptionFactory in both Server and Client to throw Derby exception subclass: Closed
• Refactor uses of DB2_JCC_MAX_EXCEPTION_PARAM_LENGTH: Closed
• Move ShutdownException into shared code area: Closed