[ http://issues.apache.org/jira/browse/DERBY-254?page=comments#action_12331396 ]
Kathey Marsden commented on DERBY-254: -------------------------------------- David said: >What I am doing (we'll see if people have comments on this) is defining a new >severity for exceptions thrown by the >network client. Since the exception >severity is mapped to the SQLException error code, the application programmer >>can check the error code to determine if it's a network client exception. I feel that the client error codes should stay as they are until changed to match the embedded severity. That in itself will be disruptive enough. Application servers use the current codes to detect stale connections, and will have to make changes when/if the codes are changed. We documented only that client SQLStates and error codes might be changed to match embedded, not that it might be changed to something else entirely. > 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
