>>It is actually becoming more and more interesting. I made bunch of other changes to fix bugs in cascading deletes/updates. Now I hope it works correctly...
>
>Hope for you too ;-)
>
>You'll have to test all scenario's though to be sure.

I tested a couple, but I'm now trying to understand, how it should work.

If we have a cascaded update, what should be our logic for our table as a child? So far I put a condition, that we check for our table as a child only in it is a first level of trigger execution, e.g. if our trigger was called as a result of cascading update on a parent, I do not run the second SCAN. However, I'm not 100% certain I'm correct.

Can somebody with the good understanding of how triggers should behave explain to me all possible scenarios?

Thanks in advance.