Subject | RE: [firebird-support] Duplicate Trigger Positions |
---|---|
Author | Kevin Stanton |
Post date | 2005-07-12T21:01:45Z |
More interesting stuff. Appears the difference is in dialects. The results
below are D1, I get NIL results with D3.
I created a 2nd before insert trigger on a table with a duplicate position
and the query reported it correctly:
RELATION TYPE SEQ COUNT
AP_CHECKS 1 0 2
Thanks again Thomas, I think we're done here!
Kevin
(RDB$TRIGGER_TYPE = 4) triggers at position 1 and three AFTER DELETE
(RDB$TRIGGER_TYPE = 6) triggers at position 1 on VESSEL, if I recall the
trigger type constants correctly.
Regards,
Thomas
[Non-text portions of this message have been removed]
below are D1, I get NIL results with D3.
I created a 2nd before insert trigger on a table with a duplicate position
and the query reported it correctly:
RELATION TYPE SEQ COUNT
AP_CHECKS 1 0 2
Thanks again Thomas, I think we're done here!
Kevin
>Hmm, the result tells you that there are three AFTER UPDATE
> This query is reporting the following:
>
> VESSEL 4 1 3
>
> VESSEL 6 1 3
(RDB$TRIGGER_TYPE = 4) triggers at position 1 and three AFTER DELETE
(RDB$TRIGGER_TYPE = 6) triggers at position 1 on VESSEL, if I recall the
trigger type constants correctly.
Regards,
Thomas
[Non-text portions of this message have been removed]