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

Kristian Waagan updated DERBY-3446:
-----------------------------------

    Attachment: derby-3446-2c_rs_getstatement_alternative.diff

Attached 'derby-3446-2c_rs_getstatement_alternative.diff', which is the same as 
2b except the tests have been removed. I don't think the tests are in the 
correct location, as they will only be executed for the embedded driver with 
the current patch. I will a also look into enabling the tests for both CPDS and 
XADS.
I will see if there is a better place for the tests.

Committed patch 2c to trunk with revision 630784.

> Make ResultSet.getStatemet 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.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.4.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
>
>
> 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.

Reply via email to