db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Van Couvering (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-254) SQLStates for SQLExceptions thrown from the client should not be null and should match embedded where possible
Date Wed, 05 Oct 2005 18:25:51 GMT
    [ http://issues.apache.org/jira/browse/DERBY-254?page=comments#action_12331418 ] 

David Van Couvering commented on DERBY-254:

OK, thanks for your comments, Kathey and Dan. 

If I could summarize: in general SQLStates and their associated severities on the network
client should match the embedded SQL States/severities on the embedded driver.  If the exception
is unique to the network client, it should still use one of the pre-defined severities in
ExceptionSeverity class.  Do I have that right?  

Thanks, also, Dan, for reminding me that the underlying SQLException classes are private interfaces
and should not be documented or depended on.  You mention that we should move towards "using
SQLException directly".  Can you explain a little more what you mean here? EmbedSQLException
and org.apache.derby.client.am.SqlException both extend java.sql.SQLException.  What does
it mean to use SQLException "directly?"

Also, if the exception are indistinguishable between embedded and network client (which makes
a lot of sense so that code is easily portable between embedded and network client), how do
we address Tomohito's concerns that (if I understand him correctly) application logic may
want to react differently depending upon whether the exception is thrown directly by the client
or indirectly from the engine?



> SQLStates for SQLExceptions thrown from the client should not be null and should match
embedded where possible
> --------------------------------------------------------------------------------------------------------------
>          Key: DERBY-254
>          URL: http://issues.apache.org/jira/browse/DERBY-254
>      Project: Derby
>         Type: Improvement
>   Components: Network Client
>     Versions:,
>     Reporter: Kathey Marsden
>     Assignee: David Van Couvering
>      Fix For:

> SQLExceptions generated from the client tend to have a null SQLState.  An evaluation
of the SQLExceptions thrown by the client needs to be performed and match embedded where possible.
> If this does not happen before the 10.1 release, it would be good to document that SQLStates
 in the client will change for future releases

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message