Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 2 of 2 total |
Execution Order Update Triggers |
Fri, May 20 2016 3:15 AM | Permanent Link |
Carl | Hi I am using multiple BEFORE UPDATE triggers by execution order on specific columns to manage the proper changes to a row... For example: For when Column1 is changed Trigger_B_U_ExecOrder_1 is fired. (BEFORE UPDATE OF "Column1") For when Column2 is changed Trigger_B_U_ExecOrder_2 is fired. (BEFORE UPDATE OF "Column2") What I have found in testing is that if the first trigger for Column1 changes Column2 (not otherwise changed), then the trigger for Column2 is fired. My assumption is that the NEWROW "buffer" is being acted upon by all the update triggers. This is sort of what I expected and it works great. The reason for posting this is to get confirmation that this is also everyone else's expectation or any other advice. Thanks, Carl |
Fri, May 20 2016 8:35 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Carl,
<< This is sort of what I expected and it works great. The reason for posting this is to get confirmation that this is also everyone else's expectation or any other advice. >> Yes, your expectations are correct. However, please be aware that the NEWROW contents in the first trigger will not be updated to reflect any changes made by another trigger *after the first trigger has already started executing*. That, and also be careful about recursive triggers.... Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Tuesday, April 30, 2024 at 03:55 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |