[ http://issues.apache.org/jira/browse/DERBY-1101?page=all ]
Knut Anders Hatlen updated DERBY-1101:
--------------------------------------
Attachment: derby-1101-v1.diff
derby-1101-v1.stat
Patch derby-1101-v1.diff modifies EmbedResultSet.getHoldability() so that it
uses getActivation() instead of getStatement(). Please let me know if you have
any comments. Thanks.
> 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
> 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
