[
https://issues.apache.org/jira/browse/DERBY-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581207#comment-13581207
]
Knut Anders Hatlen commented on DERBY-6066:
-------------------------------------------
Do you understand why the changes in TableLockBasicTest are needed? The last
part of the statement name is based on the section number, so the patch seems
to have increased the number of sections needed in this test, which sounds
counterintuitive to me.
> Client should use a prepared statement rather than regular statement for
> Connection.getTransactionIsolation
> -----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6066
> URL: https://issues.apache.org/jira/browse/DERBY-6066
> Project: Derby
> Issue Type: Improvement
> Components: Network Client
> Reporter: Mamta A. Satoor
> Assignee: Mamta A. Satoor
> Attachments: DERBY6066_patch1_diff.txt
>
>
> This jira is similar to DERBY-6053 but for
> o.a.d.client.am.Connection.getTransactionIsolation. Use prepared statement
> rather than regular statement every time user makes a get transaction
> isolation call.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
