Daniel John Debrunner (JIRA) wrote: > [ > http://issues.apache.org/jira/browse/DERBY-254?page=comments#action_12331399 > ] > >Daniel John Debrunner 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'm not sure Derby should be recommending checking the error code for an >exception, I don't think today it's specified as any part of the documentation >that the error code is a severity. Use of the error code is vendor specific >and will result in non-portable programs. JDBC 4.0 is addressing this with the >sub-classing of SQLException. > > > So with the product as is, (before JDBC 4.0) what is the recommended way to check if an exception makes a connection invalid. Currently I know there are users that are using the error codes (Exception Severity)?
The errorcode is documented as severity for embedded. http://db.apache.org/derby/docs/10.0/manuals/develop/develop86.html#IDX717 Thanks Kathey
