[
https://issues.apache.org/jira/browse/DERBY-6800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555489#comment-14555489
]
ASF subversion and git services commented on DERBY-6800:
--------------------------------------------------------
Commit 1680979 from [~bryanpendleton] in branch 'code/trunk'
[ https://svn.apache.org/r1680979 ]
DERBY-6800: Implement DerbySQLIntegrityConstraintViolationException class
This change adds the new DerbySQLIntegrityConstraintViolationException class,
which extends java.sql.SQLIntegrityConstraintViolationException, but adds
additional methods getConstraintName and getTableName.
This patch was contributed by Abhinav Gupta (abhinavgupta2004 at gmail dot com)
> Implement DerbySQLIntegrityConstraintViolationException class
> -------------------------------------------------------------
>
> Key: DERBY-6800
> URL: https://issues.apache.org/jira/browse/DERBY-6800
> Project: Derby
> Issue Type: Sub-task
> Components: JDBC
> Reporter: Bryan Pendleton
> Assignee: Abhinav Gupta
> Priority: Minor
> Attachments: subPart1.diff
>
>
> As part of DERBY-6773, we wish to build a new exception class,
> to be named DerbySQLIntegrityConstraintViolationException,
> which extends java.sql.SQLIntegrityConstraintViolationException
> but provides additional methods getConstraintName() and
> getTableName().
> This exception will be thrown by the SQLExceptionFactory classes
> in the client and in the engine, instead of the current code which
> throws SQLIntegrityConstraintViolationException
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
