Answering myself...
It may be feasible to [with little code] catch schema changes that
would invalidate DB triggers before committing them. I'm not yet sure
how to do that without re-entrance, but that may be OK too (hey,
OP_ParseSchema does it). At least I've an idea that might be worth
pursing
I've a patch that has only one bug that I'm aware of left: in
autocommit mode, a PRAGMA connect_triggers=1; will fire any connect
triggers and any before commit triggers, but not any after begin
triggers -- mildly annoying, but tolerable.
Writing tests, however, I discovered something subtle and o
2 matches
Mail list logo