[
https://issues.apache.org/jira/browse/DERBY-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587690#comment-13587690
]
Mamta A. Satoor edited comment on DERBY-6066 at 2/26/13 10:49 PM:
------------------------------------------------------------------
Committed changes to trunk with revision 1450499. We now use PreparedStatement
rather than Statement for getting the isolation level from the server. Commit
also includes comments in the code for when the call for the isolation will
actually go to the server over the wire and when it will be obtained for
client's local session cache.
was (Author: mamtas):
Committed changes to use PreparedStatement rather than Statement for
getting the isolation level from the server. Also put comments for when the
call for the isolation will actually go to the server over the wire and when it
will be obtained for client's local session cache.
> 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, DERBY6066_patch2_diff.txt,
> SampleProgram.java
>
>
> 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
