“Legacy” and “sql2003” relation triggers are exactly the same. The only thing that differs is the creation syntax.

Triggers with lower position numbers fire first. Position numbers need not be unique, but if two or more triggers have the
same position, the firing order between them is undefined.

When defining relation triggers, each mutation type (INSERT, UPDATE or DELETE) may occur at most once in the mutation list.

SQL-2003-compliant syntax for relation triggers

Added in: 2.1

Description: Since Firebird 2.1, an alternative, SQL-2003-compliant syntax can be used for triggers on tables and views. Instead of specifying
“FORrelationname” before the event type and the optional directives surrounding it, you can now put “ONrelationname” after it, as shown in the syntax earlier in this chapter.

Example:

create trigger biu_books
active before insert or update position 3
on books
as
begin
if (new.id is null)
then new.id = next value for gen_bookids;
end

Database triggers

Added in: 2.1

Description: Since Firebird 2.1, triggers can be defined to fire upon the database events CONNECT, DISCONNECT, TRANSACTION START, TRANSACTION COMMIT and TRANSACTION ROLLBACK. Only the database owner and SYSDBA can create, alter and drop these triggers.

CONNECT and DISCONNECT triggers are executed in a transaction created specifically for this purpose. If all goes well, the transaction is committed.
Uncaught exceptions roll back the transaction, and:

In the case of a CONNECT trigger, the connection is then broken and the exception returned to the client.

With a DISCONNECT trigger, exceptions are not reported and the connection is broken as foreseen.

TRANSACTION triggers are executed within the transaction whose opening, committing or rolling-back evokes them. The actions taken after
an uncaught exception depend on the type:

In a START trigger, the exception is reported to the client and the transaction is rolled back.

In a COMMIT trigger, the exception is reported, the trigger's actions so far are undone and the commit is canceled.

In a ROLLBACK trigger, the exception is not reported and the transaction is rolled back as foreseen.

It follows from the above that there is no direct way of knowing if a DISCONNECT or TRANSACTION ROLLBACK trigger caused an exception.

It also follows that you can't connect to a database if a CONNECT trigger causes an exception, and that you can't start a transaction if a TRANSACTION START trigger does so. Both phenomena effectively lock you out of your database while you need to get in there to fix the problem.
See the note below for a way around this Catch-22 situation.

In the case of a two-phase commit, TRANSACTION COMMIT triggers fire in the prepare, not the commit phase.

Note

Some Firebird command-line tools have been supplied with new switches to suppress the automatic firing of database triggers:

gbak -nodbtriggers
isql -nodbtriggers
nbackup -T

These switches can only be used by the database owner and SYSDBA.

Domains instead of datatypes

Changed in: 2.1

Description: Firebird 2.1 and up allow the use of domains instead of SQL datatypes when declaring local trigger variables. See PSQL::DECLARE for the exact syntax and details.

COLLATE in variable declarations

Changed in: 2.1

Description: Firebird 2.1 and up allow COLLATE clauses in local variable declarations. See PSQL::DECLARE for syntax and details.

NOT NULL in variable declarations

Changed in: 2.1

Description: Firebird 2.1 and up allow NOT NULL constraints in local variable declarations. See PSQL::DECLARE for syntax and details.

Multi-action triggers

Added in: 1.5

Description: Relation triggers can be defined to fire upon multiple operations (INSERT and/or UPDATE and/or DELETE). Three new boolean context variables (INSERTING, UPDATING and DELETING) have been added so you can execute code conditionally within the trigger body depending on the type of operation.

Example:

create trigger biu_parts for parts
before insert or update
as
begin
/* conditional code when inserting: */
if (inserting and new.id is null)
then new.id = gen_id(gen_partrec_id, 1);
/* common code: */
new.partname_upper = upper(new.partname);
end

Note

In multi-action triggers, both context variables OLD and NEW are always available. If you use them in the wrong situation (i.e. OLD while inserting or NEW while deleting), the following happens:

If you try to read their field values, NULL is returned.

If you try to assign values to them, a runtime exception is thrown.

BEGIN ... END blocks may be empty

Changed in: 1.5

Description: BEGIN ... END blocks may be empty in Firebird 1.5 and up, allowing you to write stub code without having to resort to dummy statements.

Example:

create trigger bi_atable for atable
active before insert position 0
as
begin
end

Multi-action triggers

Restriction on altering used triggers

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.

PLAN allowed in trigger code

Changed in: 1.5

Description: Before Firebird 1.5, a trigger containing a PLAN statement would be rejected by the compiler. Now a valid plan can be included and will be used.

ALTER TRIGGER no longer increments table change count

Changed in: 1.0

Description: Each time you use CREATE, ALTER or DROP TRIGGER, InterBase increments the metadata change counter of the associated table. Once that counter reaches 255, no more metadata
changes are possible on the table (you can still work with the data though). A backup-restore cycle is needed to reset the
counter and perform metadata operations again.

While this obligatory cleanup after many metadata changes is in itself a useful feature, it also means that users who regularly
use ALTER TRIGGER to deactivate triggers during e.g. bulk import operations are forced to backup and restore much more often then needed.

Since changes to triggers don't imply structural changes to the table itself, Firebird no longer increments the table change
counter when CREATE, ALTER or DROP TRIGGER is used. One thing has remained though: once the counter is at 255, you can no longer create, alter or drop triggers for
that table.

CREATE OR ALTER TRIGGER

Available in: DSQL

Added in: 1.5

Description: If the trigger does not yet exist, it is created just as if CREATE TRIGGER were used. If it already exists, it is altered and recompiled. Existing permissions and dependencies are preserved.

Syntax: Exactly the same as for CREATE TRIGGER.

DROP TRIGGER

Available in: DSQL, ESQL

Restriction on dropping used triggers

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.

RECREATE TRIGGER

Available in: DSQL

Added in: 2.0

Description: Creates or recreates a trigger. If a trigger with the same name already exists, RECREATE TRIGGER will try to drop it and create a new trigger. RECREATE TRIGGER will fail if the existing trigger is in use.

Restriction on recreating used triggers

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.