[
https://issues.apache.org/jira/browse/DERBY-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557304#action_12557304
]
Kristian Waagan commented on DERBY-3305:
----------------------------------------
Could the commit for this issue have caused the failure in the tinderbox test?
I don't know if it is the test that is incorrect now, or if another issue has
surfaced in the resultset code/implementation.
Note there there was also another commit before the failure occurred, but due
to problems accessing svn at the moment and no patch attached to the issue, I
can't investigate further atm.
> Embedded ResultSet.getStatement() returns incorrect reference for dynamic
> result sets
> -------------------------------------------------------------------------------------
>
> Key: DERBY-3305
> URL: https://issues.apache.org/jira/browse/DERBY-3305
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.0.0
> Reporter: Daniel John Debrunner
> Assignee: Daniel John Debrunner
> Priority: Minor
>
> ResultSets returned as dynamic results sets, ie. those created in a java
> procedure and returned via the java.sql.Statement that executed the call of
> the procedure, do not return the correct statement reference for
> getStatement. Need to return reference to statement that executed the CALL
> and returned the ResultSet instead of the statement that performed the
> executeQuery.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
