SQL Language Enhancements
Note
LEAVE | BREAK and EXIT statements can now be used in triggers.
(1.5) Valid PLAN statements can now be included in triggers
Ignacio J. Ortega
Until now, a trigger containing a PLAN statement would be rejected by the compiler. Now, a valid plan can be included and will be used.
(1.5) Empty BEGIN..END blocks
Dmitry Yemanov
Empty BEGIN..END blocks in PSQL modules are now legal. For example, you can now write "stub" modules like
CREATE TRIGGER BI_ATABLE FOR ATABLE
ACTIVE BEFORE INSERT POSITION 0
AS
BEGIN
END ^
(1.5) Declare and define local variable in single statement
Claudio Valderrama
Simplifies syntax and allows local variables to be declared and defined (or initialized) in one statement.
Syntax Pattern
DECLARE [VARIABLE] name <variable_type> [{'=' | DEFAULT} value];
Example
DECLARE my_var INTEGER = 123;
New Reserved Words
The following new Firebird keywords should be added to the list of reserved words published for InterBase 6.0.1.
BIGINT (1.5) |
CASE (1.5) |
CURRENT_CONNECTION (1.5) |
CURRENT_ROLE |
CURRENT_TRANSACTION (1.5) |
CURRENT_USER |
RECREATE |
ROW_COUNT (1.5) |
RELEASE |
SAVEPOINT |
|
|
47
SQL Language Enhancements
The following keywords are reserved for future planned use:
ABS |
BOOLEAN |
BOTH |
CHAR_LENGTH |
CHARACTER_LENGTH |
FALSE |
LEADING |
OCTET_LENGTH |
TRIM |
TRAILING |
TRUE |
UNKNOWN |
The following keywords were reserved words in Firebird 1.0 and are no longer reserved in Firebird 1.5:
BREAK |
DESCRIPTOR |
FIRST |
IIF |
SKIP |
SUBSTRING |
The following non-reserved words are recognised in 1.5 as keywords when used in their respective structural contexts:
COALESCE |
DELETING |
INSERTING |
LAST |
LEAVE |
LOCK |
NULLIF |
NULLS |
STATEMENT |
UPDATING |
USING |
|
The following new InterBase 6.5 and 7 keywords (not reserved in Firebird) should also be treated as if they were reserved, for compatibility:
BOOLEAN |
FALSE |
GLOBAL |
PERCENT |
PRESERVE |
ROWS |
TEMPORARY |
TIES |
TRUE |
48