[
https://issues.apache.org/jira/browse/DERBY-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350656#comment-14350656
]
Abhinav Gupta commented on DERBY-6773:
--------------------------------------
Hi Bryan,
I added your patch and even I am able to build the code successfully now,
thank you very much for the help. I am not very sure if I understand the
client server problem that is currently being faced, could you please
explain it to me ?
I had edited the derbyRepro class, the way you had suggested earlier. Now
when the program catches the exception, a sealing violation is being
encountered. I have attached the output [0].
Does this mean that I've to seal the package that the new exception class
is in ?
[0] : http://pastebin.com/XeMkNSpE
On Fri, Mar 6, 2015 at 8:42 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: DERBY6733Repro.java, SamePackage.diff, ant -verbose
> build all.txt
>
>
> 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)
