Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-1035

With client, Connection.getTransactionIsolation() return value is wrong after changing the isolation level with an SQL statement such as "set current isolation = RS"

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 10.1.3.1, 10.2.1.6
    • Fix Version/s: 10.1.3.1, 10.2.1.6
    • Component/s: Network Client
    • Labels:
      None

      Description

      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.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              deepa Deepa
              Reporter:
              kmarsden Katherine Marsden

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment