Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-3769

SET TRANSACTION READ ONLY not detected

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.4.17, 2.5.15, 6.1.1
    • Fix Version/s: 22.08.0
    • Component/s: qc_sqlite
    • Labels:
      None
    • Sprint:
      MXS-SPRINT-141, MXS-SPRINT-143, MXS-SPRINT-144

      Description

      MaxScale does not detect that a transaction is read-only if SET TRANSACTION READ ONLY is used instead of the explicit START TRANSACTION READ ONLY.

        Attachments

          Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MXS-3947 Read-only transaction behavior is not documented

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MXS-3980 readwritesplit not understanding SET SESSION TRANSACTION READ ONLY

          • Major - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              markus makela markus makela
              Reporter:
              markus makela markus makela
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.