Subject | Re: [Firebird-Architect] rfc: TRUNCATE TABLE |
---|---|
Author | Dmitry Yemanov |
Post date | 2008-10-22T11:02:24Z |
Adriano,
but you proposed to have the appropriate AFTER triggers for them. As far
as I see, the only thing that differs for TRUNCATE is that both BEFORE
and AFTER triggers will be semantically equivalent, as there are no
metadata modifications during the statement execution that could be seen
in the AFTER trigger.
Dmitry
> I think we should not have AFTER TRUNCATE. Because then it will beWhy? Other DDL statements also perform the most important work in DFW,
> needed to run in DFW, different from others DDL triggers.
but you proposed to have the appropriate AFTER triggers for them. As far
as I see, the only thing that differs for TRUNCATE is that both BEFORE
and AFTER triggers will be semantically equivalent, as there are no
metadata modifications during the statement execution that could be seen
in the AFTER trigger.
Dmitry