|
Posted by Seribus Dragon on 06/04/07 18:48
Why not just break up the action into three triggers? if there is
common code use a stored procedure got that part.
Hubert Trzewik wrote:
> Hi,
>
> I want to have all-in-one trigger, defined like this:
>
> CREATE TRIGGER MyInsertDeleteUpdateHandler
> ON MyTable
> FOR DELETE, INSERT, UPDATE
> AS
> BEGIN
> (...)
> END
>
> Now, how can I tell why this trigger was fired (what event caused
> trigger to be fired) - was it DELETE, INSERT or UPDATE?
>
> Is there something like this: @@event_type,
> so I could do for example IF (@@event_type = DELETE) (...)
>
> Of course I can create 3 triggers instead of 1, to be sure what event
> fired my trigger.
>
> I can also count records in _deleted_, _inserted_ tables or to do
> JOINs with it. But, _inserted_ table is common for UPDATE and INSERT
> events..
>
> Any suggestions?
> Thanks in advance.
>
> Hubert
>
Navigation:
[Reply to this message]
|