[
https://issues.apache.org/jira/browse/DERBY-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527327
]
Stan Bradbury commented on DERBY-401:
-------------------------------------
I looked up the Exceptions in the API and it seems the definitions are clear
enough to decide which should be thrown. I do not understand the reference to
SQLState class value '08' and perhaps this is the issue Knut refers to. It
seems quite intuitive that this a Connection Exception and that it will not
succeed until the failure is corrected.
Partial definitions:
java.sql.SQLNonTransientConnectionException: thrown for the SQLState class
value '08', representing that the connection operation that failed will not
succeed when the operation is retried without the cause of the failure being
corrected.
>> SQLTransientConnectionException
>From API: thrown in situations where a previoulsy failed operation might be
>able to succeed when the operation is retried without any intervention by
>application-level functionality.
> Add SQLException subclasses and throw them correctly to match JDBC 4 spec
> -------------------------------------------------------------------------
>
> Key: DERBY-401
> URL: https://issues.apache.org/jira/browse/DERBY-401
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
> Affects Versions: 10.1.1.0
> Reporter: David Van Couvering
> Priority: Minor
>
> JDBC4 defines subclasses of SQLException. Derby code should be upgraded to
> use these subclasses and throw them correctly based on the spec. I recommend
> we can start work on this even prior to JDBC 4 spec being finalized.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
