[ http://issues.apache.org/jira/browse/DERBY-953?page=all ]

Kristian Waagan updated DERBY-953:
----------------------------------

    Attachment: DERBY-953-2a.diff

'DERBY-953-2a.diff' implements EmbedStatement.isClosed() in different way. If 
the statement is marked as active, it goes to the parent connection to verify 
this. Tests have been run locally, but they are not yet submitted for commit. 
See DERBY-1097 for testing code.
Derbyall has not been run, the patch only adds new code that is not used 
anywhere yet.
Implementation is in line with the comment for the initial submission, and with 
the comments on DERBY-1095.
Nothing have been changed for the client side since the previous patch. See 
'DERBY-953-1a.stat' for svn status (unchanged).

Please review, and when acceptable, 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: 10.2.0.0
>  Attachments: DERBY-953-1a.diff, DERBY-953-1a.stat, DERBY-953-2a.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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to