db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3446) Make ResultSet.getStatemet return the correct statement when created by a logical statement
Date Thu, 21 Feb 2008 20:55:19 GMT

     [ 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-1a_rs_getstatement.stat
                derby-3446-1a_rs_getstatement.diff

'derby-3446-1a_rs_getstatement.diff' is a proposal of how to make ResultSet.getStatement return
the correct statement when using logical statements to create the result set. The changes
are pretty isolated.

I think there are alternative approaches, but when I tried one of them it caused massive code
changes to classes in both am and net. I observe that the issue is handled in a similar way
as in the patch in the embedded driver.

If you want to run the test with and without the implementing code, remember to also apply
the patch for DERBY-3329.

> 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
>
>
> 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.


Mime
View raw message