[
https://issues.apache.org/jira/browse/DERBY-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3441:
-----------------------------------
Attachment: derby-3441-1c-statement_reset.diff
'derby-3441-1c-statement_reset.diff' implements a working reset procedure for
statement pooling.
Besides the new functionality, I also had to modify some existing code that
broke statement pooling. The way things were in the existing code does not seem
correct to me, but I need more time to determine what to do about it.
Also, we should probably discuss whether the required changes should go into
10.4 or be included only in the next release.
For now I've tried to disturb as little as possible. Some cleanup will be
required later.
Since I'm going away for one week, it will have to wait until I'm back.
And I'm sorry for committing this patch so quickly, but all tests run cleanly
and it is required for testing the statement pooling feature.
Committed patch 1c to trunk with revision 632334.
> Determine and implement a proper procedure for resetting a prepared statement
> for reuse in a statement pool
> -----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3441
> URL: https://issues.apache.org/jira/browse/DERBY-3441
> Project: Derby
> Issue Type: Sub-task
> Components: JDBC, Network Client
> Affects Versions: 10.4.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.4.0.0
>
> Attachments: derby-3441-1a-statement_reset.diff,
> derby-3441-1b-statement_reset.diff, derby-3441-1c-statement_reset.diff,
> derby-3441-2a-minor_am_refactoring.diff,
> derby-3441-3a-extract_setTransactionIsolationX.diff
>
>
> Initial investigations indicate there are no existing suitable methods to
> properly reset a prepared (or callable) statement for reuse with a statement
> pool.
> A full reset is too heavy weight and defeats the purpose of statement
> pooling, but a proper procedure should be achievable by reusing existing
> pieces of code.
> Correctness is of course the most important thing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
