[
https://issues.apache.org/jira/browse/DERBY-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14506077#comment-14506077
]
Abhinav Gupta commented on DERBY-6773:
--------------------------------------
Hi Bryan,
I was studying the code and yes your solution does make sense to me, I
think I can write the code for it.
If I have understood correctly, we have to implement the getTextMessage()
method in a new java class MessageUtils, so that it can decode the
messageId to error, am I correct ?
On Sun, Apr 19, 2015 at 11:22 PM, Bryan Pendleton (JIRA) <[email protected]>
> Derby throws plain SQLIntegrityConstraintViolationException
> -----------------------------------------------------------
>
> Key: DERBY-6773
> URL: https://issues.apache.org/jira/browse/DERBY-6773
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
> Affects Versions: 10.10.2.0
> Environment: Windows 7 x86_64, Java 1.6.0.45
> Reporter: Jochen Wiedmann
> Assignee: Abhinav Gupta
> Priority: Minor
> Attachments: CallSuper.diff, DERBY6733Repro.java, SamePackage.diff,
> SharedException.diff, ant -verbose build all.txt,
> generateOnClientDoesntWork.diff
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
