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] Commented: (DERBY-953) Add miscellaneous Statement methods introduced by JDBC 4
Date Wed, 22 Mar 2006 17:51:42 GMT
    [ http://issues.apache.org/jira/browse/DERBY-953?page=comments#action_12371440 ] 

David Van Couvering commented on DERBY-953:

I could be stubborn about my point of view, but I think that's not worthwhile.  Dan has a
good point, and Kristian has also pointed out to me that there are exceptions all the way
down so there's no way to avoid catching an exception.

So I must humbly apologize to Kristian and say I think I have to agree with Dan that the first
patch is simpler and is more in line with ResultSet.isClosed().

I would like it to check for a *specific* SQL State (e.g. SQLState.NO_CURRENT_CONNECTION)
rather than swallow any old exception.   I'll make that change and commit.


> Add miscellaneous Statement methods introduced by JDBC 4
> --------------------------------------------------------
>          Key: DERBY-953
>          URL: http://issues.apache.org/jira/browse/DERBY-953
>      Project: Derby
>         Type: New Feature
>   Components: JDBC
>     Reporter: Rick Hillegas
>     Assignee: Kristian Waagan
>      Fix For:
>  Attachments: DERBY-953-1a.diff, DERBY-953-1a.stat, DERBY-953-2a.diff, DERBY-953-3a.diff
> As described in the JDBC 4 spec, sections 13.1 and 3.1.
> This adds support for new Statement methods added by JDBC4 and not addressed by other
JIRAs: isClosed() and getResultSetHoldability().

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message