Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-10142 PL/SQL parser
  3. MDEV-10588

sql_mode=ORACLE: TRUNCATE TABLE t1 [ {DROP|REUSE} STORAGE ]

Details

    • 10.2.2-3, 10.2.2-1, 10.2.2-2, 10.2.2-4, 10.1.18

    Description

      When running with sql_mode=ORACLE, MariaDB will support an optional STORAGE clause.

      Example:

      TRUNCATE TABLE t1 DROP STORAGE;

      An open question is if the parser should just consume and ignore the STORAGE clause, or the underlying engine should perform some actions, depending on the choice between DROP or REUSE.

      The default behavior is DROP STORAGE.

      Note, although REUSE is a reserved keyword in Oracle, we won't reserve it even in sql_mode=ORACLE under terms of this task, as REUSE does not introduce grammar conflicts.

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          bar Alexander Barkov created issue -
          bar Alexander Barkov made changes -
          Field Original Value New Value
          Description When running with {{sql_mode=ORACLE}}, MariaDB will support an optional {{STORAGE}} clause.

          Example:
          {code:sql}
          TRUNCATE TABLE t1 DROP STORAGE;
          {code}
          		When running with {{sql_mode=ORACLE}}, MariaDB will support an optional {{STORAGE}} clause.

          Example:
          {code:sql}
          TRUNCATE TABLE t1 DROP STORAGE;
          {code}

          An option question is that if the parser should just consume and ignore the {{STORAGE}} clause, or the underlying engine should perform some actions, depending on the choice between {{DROP}} or {{REUSE}}.
          bar Alexander Barkov made changes -
          Description When running with {{sql_mode=ORACLE}}, MariaDB will support an optional {{STORAGE}} clause.

          Example:
          {code:sql}
          TRUNCATE TABLE t1 DROP STORAGE;
          {code}

          An option question is that if the parser should just consume and ignore the {{STORAGE}} clause, or the underlying engine should perform some actions, depending on the choice between {{DROP}} or {{REUSE}}.
          		When running with {{sql_mode=ORACLE}}, MariaDB will support an optional {{STORAGE}} clause.

          Example:
          {code:sql}
          TRUNCATE TABLE t1 DROP STORAGE;
          {code}

          An option question is that if the parser should just consume and ignore the {{STORAGE}} clause, or the underlying engine should perform some actions, depending on the choice between {{DROP}} or {{REUSE}}.

          The default behavior is {{DROP STORAGE}}.
          bar Alexander Barkov made changes -
          Description When running with {{sql_mode=ORACLE}}, MariaDB will support an optional {{STORAGE}} clause.

          Example:
          {code:sql}
          TRUNCATE TABLE t1 DROP STORAGE;
          {code}

          An option question is that if the parser should just consume and ignore the {{STORAGE}} clause, or the underlying engine should perform some actions, depending on the choice between {{DROP}} or {{REUSE}}.

          The default behavior is {{DROP STORAGE}}.
          		When running with {{sql_mode=ORACLE}}, MariaDB will support an optional {{STORAGE}} clause.

          Example:
          {code:sql}
          TRUNCATE TABLE t1 DROP STORAGE;
          {code}

          An open question is that if the parser should just consume and ignore the {{STORAGE}} clause, or the underlying engine should perform some actions, depending on the choice between {{DROP}} or {{REUSE}}.

          The default behavior is {{DROP STORAGE}}.
          bar Alexander Barkov made changes -
          Description When running with {{sql_mode=ORACLE}}, MariaDB will support an optional {{STORAGE}} clause.

          Example:
          {code:sql}
          TRUNCATE TABLE t1 DROP STORAGE;
          {code}

          An open question is that if the parser should just consume and ignore the {{STORAGE}} clause, or the underlying engine should perform some actions, depending on the choice between {{DROP}} or {{REUSE}}.

          The default behavior is {{DROP STORAGE}}.
          		When running with {{sql_mode=ORACLE}}, MariaDB will support an optional {{STORAGE}} clause.

          Example:
          {code:sql}
          TRUNCATE TABLE t1 DROP STORAGE;
          {code}

          An open question is if the parser should just consume and ignore the {{STORAGE}} clause, or the underlying engine should perform some actions, depending on the choice between {{DROP}} or {{REUSE}}.

          The default behavior is {{DROP STORAGE}}.
          monty Michael Widenius made changes -
          Parent MDEV-10142 [ 56873 ]
          Issue Type Task [ 3 ] Technical task [ 7 ]
          monty Michael Widenius added a comment -

          For first version, lets just ignore the extra options for truncate that only affects performance.

          monty Michael Widenius added a comment - For first version, lets just ignore the extra options for truncate that only affects performance.
          alvinr Alvin Richards (Inactive) made changes -
          Labels Compatibility
          alvinr Alvin Richards (Inactive) made changes -
          Labels Compatibility
          alvinr Alvin Richards (Inactive) made changes -
          Labels Compatibility
          alvinr Alvin Richards (Inactive) made changes -
          Labels Compatibility
          serg Sergei Golubchik made changes -
          Labels Compatibility
          alvinr Alvin Richards (Inactive) made changes -
          Labels Compatibility Compatibility NRE-307517
          bar Alexander Barkov made changes -
          Description When running with {{sql_mode=ORACLE}}, MariaDB will support an optional {{STORAGE}} clause.

          Example:
          {code:sql}
          TRUNCATE TABLE t1 DROP STORAGE;
          {code}

          An open question is if the parser should just consume and ignore the {{STORAGE}} clause, or the underlying engine should perform some actions, depending on the choice between {{DROP}} or {{REUSE}}.

          The default behavior is {{DROP STORAGE}}.
          		When running with {{sql_mode=ORACLE}}, MariaDB will support an optional {{STORAGE}} clause.

          Example:
          {code:sql}
          TRUNCATE TABLE t1 DROP STORAGE;
          {code}

          An open question is if the parser should just consume and ignore the {{STORAGE}} clause, or the underlying engine should perform some actions, depending on the choice between {{DROP}} or {{REUSE}}.

          The default behavior is {{DROP STORAGE}}.

          Note, although {{REUSE}} is a reserved keyword in Oracle, we won't reserve it even in {{sql_mode=ORACLE}} under terms of this task, as {{REUSE}} does not introduce grammar conflicts.
          bar Alexander Barkov made changes -
          issue.field.resolutiondate 2016-11-15 11:58:37.0 2016-11-15 11:58:37.764
          bar Alexander Barkov made changes -
          Component/s Parser [ 10201 ]
          Fix Version/s 10.3.0 [ 22127 ]
          Fix Version/s 10.2 [ 14601 ]
          Assignee Alexander Barkov [ bar ]
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Closed [ 6 ]
          alvinr Alvin Richards (Inactive) made changes -
          Labels Compatibility NRE-307517 Approved Compatibility NRE-307517
          alvinr Alvin Richards (Inactive) made changes -
          NRE Projects NRE-307517
          alvinr Alvin Richards (Inactive) made changes -
          Labels Approved Compatibility NRE-307517 Approved Compatibility
          alvinr Alvin Richards (Inactive) made changes -
          NRE Approved Yes [ 10304 ]
          alvinr Alvin Richards (Inactive) made changes -
          Labels Approved Compatibility Compatibility
          bar Alexander Barkov made changes -
          Labels Compatibility Compatibility need_review
          serg Sergei Golubchik made changes -
          Labels Compatibility need_review Compatibility
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 76694 ] MariaDB v4 [ 150777 ]

          People

            bar Alexander Barkov
            bar Alexander Barkov
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.