Hello, I've been looking into the way triggers are implemented and was thinking about adding support for recursive triggers, as they would simplify my current project dramatically. What was/is the reason to leave them out?
My thoughts were adding recursive triggers by calling them like subroutines (via the VDBE Gosub and Return) on demand. I haven't thought this through, but wanted to ask if there are limitations or blocking points in doing recursive triggers this way? I know that the VDBE stack is limited and queries with very deep triggers may abort, if the stack is overflowed. Is the function sqlite3CodeRowTrigger, the only place I'd need to adjust to support recursive triggers? Thanks, Mike ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
