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, 21 Jul 2006 23:37:14 GMT
     [ http://issues.apache.org/jira/browse/DERBY-254?page=all ]

David Van Couvering resolved DERBY-254.
---------------------------------------

    Resolution: Fixed
    Derby Info:   (was: [Release Note Needed])

Resolving this issue and removing Release Note Needed as DERBY-1566 is tracking this now.

> 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
>          Issue Type: Improvement
>          Components: Network Client
>    Affects Versions: 10.2.0.0, 10.1.1.0
>            Reporter: Kathey Marsden
>         Assigned To: 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