[ http://issues.apache.org/jira/browse/DERBY-846?page=comments#action_12377472 ]
David Van Couvering commented on DERBY-846: ------------------------------------------- Hi, Kathey. In those rare cases in the network client where SqlException already has something besides null for SQLState (which only was happening when DRDA had a required specific SQL State), I have not changed those SQL States. They are still consistent with the spec, as are the error codes. The only thing that has changed in some cases are the error messages, as our messages were just too abstruse and cloaked in DRDA-speak. SQLExceptionFactory40 is responsible for throwing the right subclass of SQLException based on the type of error. It does this by looking at the SQLState. Previously it did not handle SQLStates as defined by DRDA, many of which indicate a connection exception or a warning, both of which have specific SQLException subclasses associated with them. So I modified SQLExceptionFactory40 to handle the DRDA-specified SQLStates. This ensures that the right subclass is thrown and that application code that is looking for a particular subclass gets it. David > Internationalze NetAgent to NetDatabaseMetadata40 in > org.apache.derby.client.net > -------------------------------------------------------------------------------- > > Key: DERBY-846 > URL: http://issues.apache.org/jira/browse/DERBY-846 > Project: Derby > Type: Sub-task > Components: Network Client > Reporter: David Van Couvering > Assignee: David Van Couvering > Attachments: DERBY-846-rev1.diff > -- 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
