db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John English <john.fore...@gmail.com>
Subject Re: Duplicate key feature request
Date Thu, 04 Dec 2014 10:26:09 GMT
On 02/12/2014 00:30, Rick Hillegas wrote:
> On 12/1/14 4:08 AM, John English wrote:
>> However, why not in any case consider deriving a separate subclass of
>> SQLException for the duplicate key case? It wouldn't break any existing code,
>> it's presumably easy to identify the code sites which should throw it, and it
>> would clarify exception handling in some cases.
> Hi John,
>
> Note that the SQLException which is thrown is already a refined subclass of
> SQLException. The failed insert will throw a
> java.sql.SQLIntegrityConstraintViolationException. That may help you code this
> approach to the problem.

But wouldn't this also be thrown by other causes such as a check constraint or 
foreign key violation? In such cases, an "if" statement would still be needed to 
check the actual cause.
-- 
John English

Mime
View raw message