Please be aware that the SAP SQL Anywhere Forum will be shut down on August 29th, 2024 when all it's content will be migrated to the SAP Community.
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Question tags:
question asked: 05 Apr, 06:46
question was seen: 313 times
last updated: 05 Apr, 09:31
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.