[ http://issues.apache.org/jira/browse/DERBY-1035?page=all ]
Deepa Remesh updated DERBY-1035:
--------------------------------
Fix Version: 10.2.0.0
10.1.3.0
Version: 10.1.3.0
Assign To: Deepa Remesh
> With client, Connection.getTransactionIsolation() return value is wrong after
> changing the isolation level with an SQL statement such as "set current
> isolation = RS"
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1035
> URL: http://issues.apache.org/jira/browse/DERBY-1035
> Project: Derby
> Type: Bug
> Components: Network Client
> Versions: 10.2.0.0, 10.1.3.0
> Reporter: Kathey Marsden
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0, 10.1.3.0
>
> With client, if the isolation level is set with an SQL Statement such as "SET
> CURRENT ISOLATION = RS" the value of Connection.getTransactionIsolation()
> will not be correct.
> jdbcapi/checkDataSource has tests for sending SQL statements to change the
> isolation level:
> e.g.
> s.executeUpdate("set current isolation = RS");
> printState("SQL to change isolation in local", cs1);
> I will disable these tests and reference this bug number.
> It is not really clear how to handle this without parsing the statement on
> the client side.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
