NEXT VALUE for sequence_name
You are viewing an old version of this article. View
the current version here.
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
Contents
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 VALUE
by creating the sequence with theCACHE
option. If not, everyNEXT VALUE
usage will cause changes in the storedSEQUENCE
table. - When using
NEXT VALUE
the value will be reserved at once and will not be reused, except if theSEQUENCE
was created withCYCLE
. This means that when you are usingSEQUENCE
s you have to expect gaps in the generated sequence numbers. - If one updates the
SEQUENCE
with SETVAL() or ALTER SEQUENCE ... RESTART,NEXT VALUE FOR
will 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
SEQUENCE
object. 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 VALUE
requires theINSERT
privilege.
MariaDB starting with 10.3.3
- You can also use
NEXT VALUE FOR sequence
for columnDEFAULT
.
See Also
- Sequence Overview
- CREATE SEQUENCE
- ALTER SEQUENCE
- PREVIOUS VALUE FOR
- SETVAL(). Set next value for the sequence.
- AUTO_INCREMENT
Comments
Comments loading...
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.