[
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-3a-extract_setTransactionIsolationX.diff
'derby-3441-3a-extract_setTransactionIsolationX.diff' creates an internal
setTransactionIsolationX method from the
java.sql.Connection.setTransactionIsolation. I need to set the transaction
isolation level on connection reset, and extracted the internal method to avoid
checking for a closed connection multiple times. The extraction follows a
typical pattern used in the client driver.
The logic remains unchanged.
Committed to trunk with revision 632279.
> 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-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.
