Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-38559

Atomic CoR: Variable DROP_BEFORE_CREATE_OR_REPLACE should be a flag in OLD_MODE

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Critical
    • Resolution: Unresolved
    • N/A
    • 12.3
    • Variables
    • None
    • Q1/2026 Server Development

    Description

      Implementation of atomic CREATE OR REPLACE added a variable which switches CREATE OR REPLACE to (approximately) the old non-atomic behavior:

      bb-main-atomic 24da629079767d736ab50d9fcf7c45e31062540f

              VARIABLE_NAME: DROP_BEFORE_CREATE_OR_REPLACE
              SESSION_VALUE: OFF
               GLOBAL_VALUE: OFF
        GLOBAL_VALUE_ORIGIN: COMPILE-TIME
              DEFAULT_VALUE: OFF
             VARIABLE_SCOPE: SESSION
              VARIABLE_TYPE: BOOLEAN
           VARIABLE_COMMENT: CREATE OR REPLACE should drop old tables before creating new ones. If not set then old table will be temporarly renamed until create table succeeeds. If create does not succeed the old table will be renamed back
          NUMERIC_MIN_VALUE: NULL
          NUMERIC_MAX_VALUE: NULL
         NUMERIC_BLOCK_SIZE: NULL
            ENUM_VALUE_LIST: OFF,ON
                  READ_ONLY: NO
      COMMAND_LINE_ARGUMENT: OPTIONAL
          GLOBAL_VALUE_PATH: NULL
      

      We have a standard mechanism, OLD_MODE variable, exactly for this, it should be a new flag there instead of a separate variable.

      Attachments

        Issue Links

          Activity

            People

              monty Michael Widenius
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.