[
https://issues.apache.org/jira/browse/DERBY-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361009#comment-14361009
]
Abhinav Gupta commented on DERBY-6773:
--------------------------------------
Also I was looking at your patch sharedException.diff,
At line 76 of
java.client.org.apache.derby.client.am.SQLExceptionFactory.java, where
derbyException is being called, "severity", "ferry" are a part of the
argument but haven't been declared anywhere in the code above.
In java.engine.org.apache.derby.impl.jdbc.SQLExceptionFactory.java, these
parameters have either been passed as arguments to getSQLException or have
been declared.
To address this, if I change the definition of getSQLException of the
client and get severity, messageId as arguments, won't that effect all the
files where this method is being called ?
On Sat, Mar 14, 2015 at 12:58 AM, Abhinav Gupta <[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,
> SharedException.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)
