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] Updated: (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:32 GMT
     [ http://issues.apache.org/jira/browse/DERBY-254?page=all ]

David Van Couvering updated DERBY-254:
--------------------------------------

    Derby Info: [Release Note Needed]

Proposed release note on this:

In this release, all of the client SQLExceptions now return valid SQL States rather than null.
 As much as possible, these SQL States are consistent with the SQL and DRDA standards and
are consistent with the SQL States returned by the embedded driver for the same error.  

> 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