On 11 Sep 2009, at 5:45pm, D. Richard Hipp wrote: > The second major enhancement is that SQLite now support recursive > triggers. The older non-recursive behavior of triggers is still the > default behavior. Recursive triggers are activated using the > recursive_triggers pragma. In addition to allowing triggers to call > themselves (either directly or indirectly) the new capability also > fires DELETE triggers on rows that are removed from a table as a > result of REPLACE conflict resolution processing.
May I ask what happens if SQLITE_MAX_TRIGGER_DEPTH is reached ? Is an error generated ? Is a transaction marked as failed, etc. ? Simon. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
