Hello everyone, I hope you are well.
I was checking the use of database triggers and a question came up.
When I create a trigger like this, I need to set the type of thing that it should “observe” changes, right?
I can also set a condition (which field to watch), at the trigger level (example image below):
Or I can set these conditionals at the action level (example image below):
My questions are:
1 - Is there any difference in processing or WU consumption if I insert a conditional at the trigger level (that does not use additional searches)? Or should I admit that when creating a databse trigger, the observation of the thing will occur in its entirety (any changes in any field), in this way the conditional would only serve to “condition” the trigger, preventing it from running, but not limiting its observation only to that specific field. So the charge (from running the trigger) would be the same with or without conditional?
2 - If the answer to question 1 is “No”, does this mean that I can then use the same trigger to different actions, creating conditional actions based on changes in different fields (if needed), and all these conditionals would be checked whenever any change (in any field) to the thing is made?
Thanks in advance! 