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

Add catchall to all table partitioning for list partitions

Details

    Description

      Not all table partitioning has the ability to add a so called "catch all". The catch all is present in range partitioning:
      partition last values less than(MAXVALUE)

      The proposal is to add similar statements to list partitioning: Proposed syntax:
      partition last values not in other

      Benefits: No more insert exceptions, giving the DBA more choices in applying this partitioning with less effort.

      Oracle uses the following syntax for this:

      CREATE TABLE h2 (c1 NUMBER,c2 NUMBER)
      PARTITION BY LIST(c1) (
      PARTITION p0 VALUES (1, 4, 7),
      PARTITION p1 VALUES (2, 5, 8),
      PARTITION p3 VALUES(DEFAULT)

      We should probably use the DEFAULT syntax for this.

      Attachments

        Issue Links

          Activity

            Norbert van Nobelen Norbert van Nobelen created issue -
            monty Michael Widenius made changes -
            Field Original Value New Value
            Description Not all table partitioning has the ability to add a so called "catch all". The catch all is present in range partitioning:
            partition last values less than(MAXVALUE)

            The proposal is to add similar statements to list partitioning: Proposed syntax:
            partition last values not in other

            Benefits: No more insert exceptions, giving the DBA more choices in applying this partitioning with less effort.

            Not all table partitioning has the ability to add a so called "catch all". The catch all is present in range partitioning:
            partition last values less than(MAXVALUE)

            The proposal is to add similar statements to list partitioning: Proposed syntax:
            partition last values not in other

            Benefits: No more insert exceptions, giving the DBA more choices in applying this partitioning with less effort.

            Oracle uses the following syntax for this:

            CREATE TABLE h2 (c1 NUMBER,c2 NUMBER)
            PARTITION BY LIST(c1) (
            PARTITION p0 VALUES (1, 4, 7),
            PARTITION p1 VALUES (2, 5, 8),
            PARTITION p3 VALUES(DEFAULT)

            We should probably use the DEFAULT syntax for this.
            monty Michael Widenius made changes -
            monty Michael Widenius made changes -
            Assignee Oleksandr Byelkin [ sanja ]
            alvinr Alvin Richards (Inactive) made changes -
            Labels Compatibility
            ratzpo Rasmus Johansson (Inactive) made changes -
            Sprint Compatibility-1 [ 88 ]
            ratzpo Rasmus Johansson (Inactive) made changes -
            Fix Version/s 10.2 [ 14601 ]
            ratzpo Rasmus Johansson (Inactive) made changes -
            Sprint Compatibility-1 [ 88 ] 10.2.2-1 [ 89 ]
            ratzpo Rasmus Johansson (Inactive) made changes -
            Rank Ranked higher
            sanja Oleksandr Byelkin made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            ratzpo Rasmus Johansson (Inactive) made changes -
            Sprint 10.2.2-1 [ 89 ] 10.2.2-1, 10.2.2-2 [ 89, 92 ]
            ratzpo Rasmus Johansson (Inactive) made changes -
            Rank Ranked lower
            sanja Oleksandr Byelkin made changes -
            Assignee Oleksandr Byelkin [ sanja ] Michael Widenius [ monty ]
            Status In Progress [ 3 ] In Review [ 10002 ]
            sanja Oleksandr Byelkin made changes -
            sanja Oleksandr Byelkin made changes -
            Assignee Michael Widenius [ monty ] Oleksandr Byelkin [ sanja ]
            sanja Oleksandr Byelkin made changes -
            Status In Review [ 10002 ] Stalled [ 10000 ]
            sanja Oleksandr Byelkin made changes -
            Fix Version/s 10.2.3 [ 22115 ]
            Fix Version/s 10.2 [ 14601 ]
            Resolution Fixed [ 1 ]
            Status Stalled [ 10000 ] Closed [ 6 ]
            sanja Oleksandr Byelkin made changes -
            Fix Version/s 10.2.2 [ 22013 ]
            Fix Version/s 10.2.3 [ 22115 ]
            elenst Elena Stepanova made changes -
            elenst Elena Stepanova made changes -
            alvinr Alvin Richards (Inactive) made changes -
            Labels Compatibility Approved Compatibility
            alvinr Alvin Richards (Inactive) made changes -
            Labels Approved Compatibility Compatibility
            alvinr Alvin Richards (Inactive) made changes -
            Labels Compatibility Approved Compatibility
            alvinr Alvin Richards (Inactive) made changes -
            Epic Link MDEV-10872 [ 58182 ]
            Krishnadas Krishnadas made changes -
            Attachment MDEV-8348.zip [ 42679 ]
            alvinr Alvin Richards (Inactive) made changes -
            Labels Approved Compatibility 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
            elenst Elena Stepanova made changes -
            elenst Elena Stepanova made changes -
            monty Michael Widenius made changes -
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 70100 ] MariaDB v4 [ 132638 ]

            People

              sanja Oleksandr Byelkin
              Norbert van Nobelen Norbert van Nobelen
              Votes:
              0 Vote for this issue
              Watchers:
              6 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.