You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org> on 2006/04/06 08:57:58 UTC

[jira] Resolved: (DERBY-1101) ResultSet.getHoldabilty will return incorrect value when the ResultSet is obtained from a procedure call

     [ http://issues.apache.org/jira/browse/DERBY-1101?page=all ]
     
Knut Anders Hatlen resolved DERBY-1101:
---------------------------------------

    Fix Version: 10.2.0.0
     Resolution: Fixed

Thanks for committing the patch, Dan! I had forgotten that it was there myself. Please close the issue if you think it is resolved.

> ResultSet.getHoldabilty will return incorrect value when the ResultSet is obtained from a procedure call
> --------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-1101
>          URL: http://issues.apache.org/jira/browse/DERBY-1101
>      Project: Derby
>         Type: Bug

>   Components: JDBC
>     Versions: 10.2.0.0
>     Reporter: Daniel John Debrunner
>     Assignee: Knut Anders Hatlen
>     Priority: Minor
>      Fix For: 10.2.0.0
>  Attachments: derby-1101-testcase-v1.diff, derby-1101-v1.diff, derby-1101-v1.stat, testderby1101.java
>
> EmbedResultSet40.getHoldability returns the holdability of the statement returned by ResultSet.getStatement().
> When a ResultSet is created by a procedure call, its holdability may not match the holdability of the Statement  that called the procedure, which is probably what ResultSet.getStatement() should return.
> This may not be exposed as a bug yet, but I think this method should be directly obtaining the holdability of the ResultSet using the Activation.getResultSetHoldability() method, rather than through a Statement. Seems a safer approach.

-- 
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