Details

    Description

      Add support for SEQUENCES, like in PostgreSQL or Oracle:

      CREATE [ TEMPORARY | TEMP ] SEQUENCE name [ INCREMENT [ BY ] increment ]
          [ MINVALUE minvalue | NO MINVALUE ] [ MAXVALUE maxvalue | NO MAXVALUE ]
          [ START [ WITH ] start ] [ CACHE cache ] [ [ NO ] CYCLE ]
      

      See https://www.postgresql.org/docs/8.1/static/sql-createsequence.html
      for details.

      The main part of the task is to add support for sequence tables in the storage engine interface. The main difference between transactional tables are only that they don't roll back when issuing a ROLLBACK statement.

      Example:

      CREATE SEQUENCE s1;
      SELECT s1.NEXTVAL FROM DUAL;
      

      Supported statements:

      • CREATE SEQUENCE
      • DROP SEQUENCE
      • ALTER SEQUENCE
      • NEXT VALUE FOR sequence_name and NEXTVAL(sequence_name)
      • PREVIOUS VALUE FOR sequence_name and LASTVAL(sequence_name)
      • SETVAL(sequence_name, next_value, is_used, round)
      • SHOW CREATE SEQUENCE

      Attachments

        Issue Links

          Activity

            monty Michael Widenius created issue -
            monty Michael Widenius made changes -
            Field Original Value New Value
            Epic Link MDEV-10137 [ 56868 ]
            serg Sergei Golubchik made changes -
            Summary Support for SEQUENCE tables Support for SEQUENCE objects
            bar Alexander Barkov made changes -
            Description Add support for SEQUENCES, like in PostgreSQL or Oracle:


            CREATE [ TEMPORARY | TEMP ] SEQUENCE name [ INCREMENT [ BY ] increment ]
                [ MINVALUE minvalue | NO MINVALUE ] [ MAXVALUE maxvalue | NO MAXVALUE ]
                [ START [ WITH ] start ] [ CACHE cache ] [ [ NO ] CYCLE ]

            See https://www.postgresql.org/docs/8.1/static/sql-createsequence.html
            for details.

            The main part of the task is to add support for sequence tables in the storage engine interface. The main difference between transactional tables are only that they don't roll back when issuing a ROLLBACK statement.
            Add support for SEQUENCES, like in PostgreSQL or Oracle:


            CREATE [ TEMPORARY | TEMP ] SEQUENCE name [ INCREMENT [ BY ] increment ]
                [ MINVALUE minvalue | NO MINVALUE ] [ MAXVALUE maxvalue | NO MAXVALUE ]
                [ START [ WITH ] start ] [ CACHE cache ] [ [ NO ] CYCLE ]

            See https://www.postgresql.org/docs/8.1/static/sql-createsequence.html
            for details.

            The main part of the task is to add support for sequence tables in the storage engine interface. The main difference between transactional tables are only that they don't roll back when issuing a ROLLBACK statement.

            Example:
            {code:sql}
            CREATE SEQUENCE s1;
            SELECT s1.NEXTVAL FROM DUAL;
            {code}
            alvinr Alvin Richards (Inactive) made changes -
            Labels Compatibility
            alvinr Alvin Richards (Inactive) made changes -
            Labels Compatibility
            serg Sergei Golubchik made changes -
            Fix Version/s 10.3 [ 22126 ]
            Fix Version/s 10.2 [ 14601 ]
            serg Sergei Golubchik made changes -
            serg Sergei Golubchik made changes -
            Description Add support for SEQUENCES, like in PostgreSQL or Oracle:


            CREATE [ TEMPORARY | TEMP ] SEQUENCE name [ INCREMENT [ BY ] increment ]
                [ MINVALUE minvalue | NO MINVALUE ] [ MAXVALUE maxvalue | NO MAXVALUE ]
                [ START [ WITH ] start ] [ CACHE cache ] [ [ NO ] CYCLE ]

            See https://www.postgresql.org/docs/8.1/static/sql-createsequence.html
            for details.

            The main part of the task is to add support for sequence tables in the storage engine interface. The main difference between transactional tables are only that they don't roll back when issuing a ROLLBACK statement.

            Example:
            {code:sql}
            CREATE SEQUENCE s1;
            SELECT s1.NEXTVAL FROM DUAL;
            {code}
            Add support for SEQUENCES, like in PostgreSQL or Oracle:

            {code:sql}
            CREATE [ TEMPORARY | TEMP ] SEQUENCE name [ INCREMENT [ BY ] increment ]
                [ MINVALUE minvalue | NO MINVALUE ] [ MAXVALUE maxvalue | NO MAXVALUE ]
                [ START [ WITH ] start ] [ CACHE cache ] [ [ NO ] CYCLE ]
            {code}
            See https://www.postgresql.org/docs/8.1/static/sql-createsequence.html
            for details.

            The main part of the task is to add support for sequence tables in the storage engine interface. The main difference between transactional tables are only that they don't roll back when issuing a ROLLBACK statement.

            Example:
            {code:sql}
            CREATE SEQUENCE s1;
            SELECT s1.NEXTVAL FROM DUAL;
            {code}
            alvinr Alvin Richards (Inactive) made changes -
            monty Michael Widenius made changes -
            Epic Link MDEV-10137 [ 56868 ]
            alvinr Alvin Richards (Inactive) made changes -
            alvinr Alvin Richards (Inactive) made changes -
            alvinr Alvin Richards (Inactive) made changes -
            alvinr Alvin Richards (Inactive) made changes -
            alvinr Alvin Richards (Inactive) made changes -
            alvinr Alvin Richards (Inactive) made changes -
            alvinr Alvin Richards (Inactive) made changes -
            Labels NRE-307517
            ratzpo Rasmus Johansson (Inactive) made changes -
            Assignee Marko Mäkelä [ marko ]
            alvinr Alvin Richards (Inactive) made changes -
            NRE Projects NRE-307517
            alvinr Alvin Richards (Inactive) made changes -
            Labels NRE-307517
            stephane@skysql.com VAROQUI Stephane made changes -
            serg Sergei Golubchik made changes -
            monty Michael Widenius made changes -
            Assignee Marko Mäkelä [ marko ] Michael Widenius [ monty ]
            monty Michael Widenius made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            bar Alexander Barkov made changes -
            Fix Version/s 10.3.0 [ 22127 ]
            Fix Version/s 10.3 [ 22126 ]
            bar Alexander Barkov made changes -
            Component/s OTHER [ 10125 ]
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Closed [ 6 ]
            bar Alexander Barkov made changes -
            monty Michael Widenius made changes -
            Description Add support for SEQUENCES, like in PostgreSQL or Oracle:

            {code:sql}
            CREATE [ TEMPORARY | TEMP ] SEQUENCE name [ INCREMENT [ BY ] increment ]
                [ MINVALUE minvalue | NO MINVALUE ] [ MAXVALUE maxvalue | NO MAXVALUE ]
                [ START [ WITH ] start ] [ CACHE cache ] [ [ NO ] CYCLE ]
            {code}
            See https://www.postgresql.org/docs/8.1/static/sql-createsequence.html
            for details.

            The main part of the task is to add support for sequence tables in the storage engine interface. The main difference between transactional tables are only that they don't roll back when issuing a ROLLBACK statement.

            Example:
            {code:sql}
            CREATE SEQUENCE s1;
            SELECT s1.NEXTVAL FROM DUAL;
            {code}
            Add support for SEQUENCES, like in PostgreSQL or Oracle:

            {code:sql}
            CREATE [ TEMPORARY | TEMP ] SEQUENCE name [ INCREMENT [ BY ] increment ]
                [ MINVALUE minvalue | NO MINVALUE ] [ MAXVALUE maxvalue | NO MAXVALUE ]
                [ START [ WITH ] start ] [ CACHE cache ] [ [ NO ] CYCLE ]
            {code}
            See https://www.postgresql.org/docs/8.1/static/sql-createsequence.html
            for details.

            The main part of the task is to add support for sequence tables in the storage engine interface. The main difference between transactional tables are only that they don't roll back when issuing a ROLLBACK statement.

            Example:
            {code:sql}
            CREATE SEQUENCE s1;
            SELECT s1.NEXTVAL FROM DUAL;
            {code}

            Supported statements:
            - CREATE SEQUENCE
            - DROP SEQUENCE
            - ALTER SEQUENCE
            - NEXT VALUE FOR sequence_name and NEXTVAL(sequence_name)
            - PREVIOUS VALUE FOR sequence_name and LASTVAL(sequence_name)
            - SETVAL(sequence_name, next_value, is_used, round)
            - SHOW CREATE SEQUENCE
            anikitin Andrii Nikitin (Inactive) made changes -
            monty Michael Widenius made changes -
            Resolution Fixed [ 1 ]
            Status Closed [ 6 ] Stalled [ 10000 ]
            monty Michael Widenius made changes -
            Status Stalled [ 10000 ] In Progress [ 3 ]
            anikitin Andrii Nikitin (Inactive) made changes -
            anikitin Andrii Nikitin (Inactive) made changes -
            anikitin Andrii Nikitin (Inactive) made changes -
            serg Sergei Golubchik made changes -
            Fix Version/s 10.3 [ 22126 ]
            Fix Version/s 10.3.0 [ 22127 ]
            serg Sergei Golubchik made changes -
            serg Sergei Golubchik made changes -
            alvinr Alvin Richards (Inactive) made changes -
            NRE Approved Yes [ 10304 ]
            monty Michael Widenius made changes -
            anikitin Andrii Nikitin (Inactive) made changes -
            anikitin Andrii Nikitin (Inactive) made changes -
            anikitin Andrii Nikitin (Inactive) made changes -
            elenst Elena Stepanova made changes -
            Component/s Sequences [ 14009 ]
            Component/s OTHER [ 10125 ]
            ralf.gebhardt Ralf Gebhardt made changes -
            Labels 10.3-beta
            serg Sergei Golubchik made changes -
            Priority Major [ 3 ] Critical [ 2 ]
            julien.fritsch Julien Fritsch made changes -
            Epic Link MDEV-11070 [ 58519 ]
            axel Axel Schwenke made changes -
            anikitin Andrii Nikitin (Inactive) made changes -
            marko Marko Mäkelä made changes -
            svoj Sergey Vojtovich made changes -
            marko Marko Mäkelä made changes -
            monty Michael Widenius made changes -
            monty Michael Widenius made changes -
            Fix Version/s 10.3.1 [ 22532 ]
            Fix Version/s 10.3 [ 22126 ]
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Closed [ 6 ]
            monty Michael Widenius made changes -
            monty Michael Widenius made changes -
            monty Michael Widenius made changes -
            monty Michael Widenius made changes -
            monty Michael Widenius made changes -
            monty Michael Widenius made changes -
            monty Michael Widenius made changes -
            monty Michael Widenius made changes -
            ralf.gebhardt Ralf Gebhardt made changes -
            NRE Approved Yes [ 10304 ]
            anel Anel Husakovic made changes -
            pramod.mahto@mariadb.com Pramod Mahto made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 75809 ] MariaDB v4 [ 132884 ]
            marko Marko Mäkelä made changes -
            danblack Daniel Black made changes -

            People

              monty Michael Widenius
              monty Michael Widenius
              Votes:
              12 Vote for this issue
              Watchers:
              28 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.