Subject | Re: [firebird-support] Trigger position question |
---|---|
Author | Ann W. Harrison |
Post date | 2004-12-08T17:58:50Z |
At 05:24 AM 12/7/2004, Daniel Jimenez wrote:
cute to rude. Nando said something that I'll like to underscore.
The order of execution of triggers that don't specify a position is
undefined and may change from version to version. As it happens,
the current code treats no position like zero, but that's an artifact
of the algorithm, not a part of the design. Similarly, if you have
two triggers defined for the same operation with the same position,
the will currently fire in alphabetical order. Don't count on either
behavior being stable across versions of Firebird, even minor versions.
Regards,
Ann
>When I define a trigger, if I omit the position statement and other triggersMy last answer was in the cryptic section of the line that runs from
>for the same table exist, will the trigger with no position statement be the
>last or the first.
cute to rude. Nando said something that I'll like to underscore.
The order of execution of triggers that don't specify a position is
undefined and may change from version to version. As it happens,
the current code treats no position like zero, but that's an artifact
of the algorithm, not a part of the design. Similarly, if you have
two triggers defined for the same operation with the same position,
the will currently fire in alphabetical order. Don't count on either
behavior being stable across versions of Firebird, even minor versions.
Regards,
Ann