[
https://issues.apache.org/jira/browse/DERBY-6804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14661303#comment-14661303
]
Abhinav Gupta commented on DERBY-6804:
--------------------------------------
Hi Bryan,
engine.SQLExceptionFactory still calls the
SQLIntegrityConstraintViolationException, instead of
DerbySQLIntegrityConstraintViolationException, I think we need to change that
before we commit this work.
> Change SQLExceptionFactory in both Server and Client to throw Derby exception
> subclass
> --------------------------------------------------------------------------------------
>
> Key: DERBY-6804
> URL: https://issues.apache.org/jira/browse/DERBY-6804
> Project: Derby
> Issue Type: Sub-task
> Components: JDBC, Network Client, Network Server
> Reporter: Bryan Pendleton
> Assignee: Abhinav Gupta
> Priority: Minor
>
> We would like the SQLExceptionFactory in both the engine and in
> the client to be changed so that instead of throwing a simple
> SQLIntegrityConstraintViolationException, it instead throws a
> DerbySQLIntegrityConstraintViolationException, which holds the
> arguments specifying the table name and constraint name of
> the constraint which was violated.
> Note that this subclass represents the first real change of behavior
> that a Derby application could notice; the previous subtasks have
> all been internal refactorings of the code to prepare for this change.
> As part of this task, we also want to provide additional regression
> tests demonstrating that the new exception can be caught and
> examined in both embedded and client-server configurations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
