Is it possible to somehow emulate the self_recursion option in the Watcom-SQL dialect for a trigger?
I would like to completely eliminate the possibility of recursively calling a trigger ("Triggers firing themselves").
Well, the obious easy answer is to prevent recursive trigger calls by adding conditions that prevent further calls. 😉
If that option does not impact Watcom-SQL triggers, you might use the stack trace functions/procedures to rollback the trigger once a particular stack level has been reached. (I do not know how that does impact performance...)
As a protective measure, SQLE_NESTING_TOO_DEEP is reported for unbounded recursive triggers (or procedures). This can be seen with a table with a DEFAULT TIMESTAMP column and an UPDATE trigger. Note: This impacts Windows after SP1 when microsecond TIMESTAMP support was added.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.