Details

    • Technical task
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • None
    • OTHER

    Description

      When running with sql_mode=ORACLE, MariaDB should emulate Oracle-style transaction related behavior:

      • No explicit transaction start (e.g. BEGIN or START statement) is needed.
        Transactions start automatically and last until COMMIT or ROLLBACK.
        This looks to be equal to SET AUTOCOMMIT=0.
      • The BEGIN keyword should always start a code block (a compound statement), even outside of a stored procedure.

      Attachments

        Activity

          monty Michael Widenius added a comment - - edited

          I assume the an easy solution is that we set autocommit=0 when changing mode to Oracle.

          In 10.2, we already support compound statements with BEGIN NOT ATOMIC.

          The MariaDB syntax, when, running in autocommit=0 mode, is:

          begin not atomic select 1 ; end ; commit |

          While Oracle syntax is:

          begin select 1 ; end ; commit |

          monty Michael Widenius added a comment - - edited I assume the an easy solution is that we set autocommit=0 when changing mode to Oracle. In 10.2, we already support compound statements with BEGIN NOT ATOMIC. The MariaDB syntax, when, running in autocommit=0 mode, is: begin not atomic select 1 ; end ; commit | While Oracle syntax is: begin select 1 ; end ; commit |

          People

            Unassigned Unassigned
            bar Alexander Barkov
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

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