| Subject | Re: Triggers in Firebird, why row based? |
|---|---|
| Author | Thomas |
| Post date | 2011-07-03T22:26:34Z |
--- In firebird-support@yahoogroups.com, "firebirdsql" <firebirdsql@...> wrote:
Most DBMS support both a row and a statement level execution, of the trigger. As far as I know SQL Server (and Sybase) is the only DBMS that is limited to only statement level ("set based") triggers.
In Oracle a row level trigger is the default if nothing else is specified.
DB2 supports row and statement level triggers.
In PostgreSQL a statement level trigger is the default, but there is no concept of a "set". You only have access to the modified data in a row level trigger.
MySQL and HSQLDB only support row level triggers.
> Every database venders seems to implement triggers per set operationDefine "every".
Most DBMS support both a row and a statement level execution, of the trigger. As far as I know SQL Server (and Sybase) is the only DBMS that is limited to only statement level ("set based") triggers.
In Oracle a row level trigger is the default if nothing else is specified.
DB2 supports row and statement level triggers.
In PostgreSQL a statement level trigger is the default, but there is no concept of a "set". You only have access to the modified data in a row level trigger.
MySQL and HSQLDB only support row level triggers.