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] Resolved: (DERBY-254) SQLStates for SQLExceptions thrown from the client should not be null and should match embedded where possible
Date Fri, 09 Jun 2006 00:19:31 GMT
     [ http://issues.apache.org/jira/browse/DERBY-254?page=all ]
     
David Van Couvering resolved DERBY-254:
---------------------------------------

    Resolution: Fixed

All client messages have been converted to use SQL States as part of the DERBY-400 work, which
is now complete except for some additional testing and documentation

> 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: 10.2.0.0, 10.1.1.0
>     Reporter: Kathey Marsden
>     Assignee: David Van Couvering
>      Fix For: 10.2.0.0

>
> 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message