[
https://issues.apache.org/jira/browse/DERBY-6800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551699#comment-14551699
]
Bryan Pendleton commented on DERBY-6800:
----------------------------------------
I feel like we're ready to move ahead with this infrastructure class, it
looks fine to me. Note that nothing will be using this class until we
complete some of the other sub-tasks of DERBY-6773, but by getting
this infrastructure in place, we make incremental progress toward our goal.
I'm intending to move ahead with committing this patch, once we have
arranged to get an ICLA in place from Abhinav.
> 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)
