[
https://issues.apache.org/jira/browse/DERBY-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3446:
-----------------------------------
Derby Info: (was: [Patch Available])
Fix Version/s: (was: 10.4.1.3)
10.5.0.0
10.4.1.4
Summary: Make ResultSet.getStatement return the correct statement
when created by a logical statement (was: Make ResultSet.getStatemet return
the correct statement when created by a logical statement)
Committed patch 3a to trunk with revision 673327.
Backported to 10.4 with revision 673329.
Updated fix versions and fixed typo in the summary.
The addition of the test concludes the work on this issue.
> Make ResultSet.getStatement return the correct statement when created by a
> logical statement
> --------------------------------------------------------------------------------------------
>
> Key: DERBY-3446
> URL: https://issues.apache.org/jira/browse/DERBY-3446
> Project: Derby
> Issue Type: Task
> Components: JDBC, Network Client
> Affects Versions: 10.4.1.3
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.4.1.4, 10.5.0.0
>
> Attachments: derby-3446-1a_rs_getstatement.diff,
> derby-3446-1a_rs_getstatement.stat,
> derby-3446-2a_rs_getstatement_alternative.diff,
> derby-3446-2a_rs_getstatement_alternative.stat,
> derby-3446-2b_rs_getstatement_alternative.diff,
> derby-3446-2c_rs_getstatement_alternative.diff,
> derby-3446-3a-stmtpool_test.diff
>
>
> ResultSet.getStatement must return the correct statement, that is the
> statement that created the result set.
> It is particularly important for result set created by logical statements, as
> leaking of physical statements can cause all kinds of side effects in a
> connection pooling environment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
