db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-401) Add SQLException subclasses and throw them correctly to match JDBC 4 spec
Date Fri, 14 Sep 2007 16:23:32 GMT

    [ https://issues.apache.org/jira/browse/DERBY-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527558

Kathey Marsden commented on DERBY-401:

Knut said:
>As it is now, it decides
>based on which package the error was detected in. I think we need to
>change this so that 58009 is thrown if the client receives invalid
>data from the server, and 08006 if the connection is lost. If we
>change it this way, Kathey's example will throw
>SQLNonTransientConnectionException (and match SQL+DRDA).

Well, I think currently it would return SQLTransientConnectionException, because of DERBY-3075,
but assuming that is fixed, it would resolve this particular situation, but I still think
that all  client errors with errorcode -4999 including 58009 and server errors with SESSION_SEVERITY
or greater should throw a SQLNonTransientConnectionException for  completeness.

> Add SQLException subclasses and throw them correctly to match JDBC 4 spec
> -------------------------------------------------------------------------
>                 Key: DERBY-401
>                 URL: https://issues.apache.org/jira/browse/DERBY-401
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>    Affects Versions:
>            Reporter: David Van Couvering
>            Priority: Minor
> JDBC4 defines subclasses of SQLException.  Derby code should be upgraded to use these
subclasses and throw them correctly based on the spec.  I recommend we can start work on this
even prior to JDBC 4 spec being finalized.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message