NEXT VALUE for sequence_name
MariaDB starting with 10.3
SEQUENCEs were introduced in MariaDB 10.3
Syntax
NEXT VALUE FOR sequence
or
NEXTVAL(sequence_name)
or in Oracle mode (SQL_MODE=ORACLE)
sequence_name.nextval
NEXT VALUE FOR is ANSI SQL syntax while NEXTVAL() is PostgreSQL syntax.
Description
Generate next value for a SEQUENCE.
- You can greatly speed up
NEXT VALUEby creating the sequence with theCACHEoption. If not, everyNEXT VALUEusage will cause changes in the storedSEQUENCEtable. - When using
NEXT VALUEthe value will be reserved at once and will not be reused, except if theSEQUENCEwas created withCYCLE. This means that when you are usingSEQUENCEs you have to expect gaps in the generated sequence numbers. - If one updates the
SEQUENCEwith SETVAL() or ALTER SEQUENCE ... RESTART,NEXT VALUE FORwill notice this and start from the next requested value. -
FLUSH TABLES will close the sequence and the next sequence number generated will be according to what's stored in the
SEQUENCEobject. In effect, this will discard the cached values. - A server restart (or closing the current connection) also causes a drop of all cached values. The cached sequence numbers are reserved only for the current connection.
-
NEXT VALUErequires theINSERTprivilege.
MariaDB starting with 10.3.3
- You can also use
NEXT VALUE FOR sequencefor columnDEFAULT.
See Also
- Sequence Overview
- CREATE SEQUENCE
- ALTER SEQUENCE
- PREVIOUS VALUE FOR
- SETVAL(). Set next value for the sequence.
- AUTO_INCREMENT
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.
© 2021 MariaDB
Licensed under the Creative Commons Attribution 3.0 Unported License and the GNU Free Documentation License.
https://mariadb.com/kb/en/next-value-for-sequence_name/