Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Avoiding multiple cascade paths
Message
 
 
À
22/08/2008 15:17:50
Information générale
Forum:
Microsoft SQL Server
Catégorie:
Conception bases de données
Versions des environnements
SQL Server:
SQL Server 2005
Divers
Thread ID:
01340693
Message ID:
01341228
Vues:
12
Yes, so will UPDATE trigger.

>
>I added a check for @@ROWCOUNT > 0 in the trigger which cured the problem. So would, for instance. a DELETE trigger fire even if there were no actual deletions ?
>
>Regards,
>Viv
>
>>A trigger fires once per SQL statement regardless of how many records are affected by the statement.
>>You may want or required to take some action in a trigger when 0 record are affected.
>>
>>>
>>>I was looking at using the 'INSTEAD OF' trigger but this in an AFTER is simpler. The only thing that threw me for a while was that the trigger fired when there was nothing to insert (ie INSERT INTO ...... (SELECT ......) caused the trigger to fire even if the select returned no records - that didn't seem very logical to me?
>>>
--sb--
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform