Firebird 2.1 Language Reference Update

Added in: 1.0
DDL statements
Description: Creates or recreates a stored procedure. If a procedure with the same name already exists, RECRE-
ATE PROCEDURE will try to drop it and create a new procedure. RECREATE PROCEDURE will fail if the existing
SP is in use.
Syntax: Exactly the same as CREATE PROCEDURE.
Restriction on recreating used procedures
Changed in: 2.0, 2.0.1
Description: In Firebird 2.0 only, a restriction is in place which prevents anyone from dropping, altering or
recreating a trigger or stored procedure if it has been used since the database was opened. This restriction has
been removed again in version 2.0.1. Still, performing these operations on a live database is potentially risky
and should only be done with the utmost care.
CREATE SEQUENCE
Available in: DSQL
Added in: 2.0
SEQUENCE or GENERATOR
Description: Creates a new sequence or generator. SEQUENCE is the SQL-compliant term for what InterBase
and Firebird have always called a generator. CREATE SEQUENCE is fully equivalent to CREATE GENERATOR
and is the recommended syntax from Firebird 2.0 onward.
Syntax:
Example:
CREATE SEQUENCE sequence-name
create sequence seqtest
Because internally sequences and generators are the same thing, you can freely mix the generator and sequence
syntaxes, even when operating on the same object. This is not recommended however.
Sequences (or generators) are always stored as 64-bit integer values, regardless of the database dialect. However:
• If the client dialect is set to 1, the server passes generator values as truncated 32-bit values to the client.
• If generator values are fed into a 32-bit field or variable, all goes well until the actual value exceeds the 32-bit
range. At that point, a dialect 3 database will raise an error whereas a dialect 1 database will silently truncate
the value (which could also lead to an error, e.g. if the receiving field has a unique key defined on it).
See also: ALTER SEQUENCE, NEXT VALUE FOR, DROP SEQUENCE
34