db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-1111) getStatement() for a ResultSet returned from a procedure in embedded mode must return the Statement that executed the CALL procedure
Date Wed, 09 Jan 2008 17:34:33 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel John Debrunner closed DERBY-1111.
----------------------------------------

    Resolution: Duplicate

Duplicate of DERBY-3305, changes are being made under that issue.

> getStatement() for a ResultSet returned from a procedure in embedded mode must return
the Statement that executed the CALL procedure
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1111
>                 URL: https://issues.apache.org/jira/browse/DERBY-1111
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, SQL
>            Reporter: Daniel John Debrunner
>
> Currently the getStatement() call for such a ResultSet will return a reference ot the
Statement object  that created the ResultSet using server-side JDBC within the procedure.

> SQL Standard 2003, part 13 indicates that a copy of the server-side JDBC ResultSet is
made by the database engine as a cursor, and in fact the server-side ResultSet is closed.
The cursor would then be returned to the client as for any other cursor, converted to a ResultSet
for JDBC.
> Derby optimizes this copying by returning the original ResultSet  through the embedded
driver, but switching its ownership to the Statement that invokved CALL procedure. This ownership
switch however does not switch the application statement returned by getStatement.
> See also http://issues.apache.org/jira/browse/DERBY-1101#action_12370189
> Fixing this will expose DERBY-1101 in JDBC 4.0

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message