The reason to delay connection trigger firing to the first non-pragma statement would be to allow one to enable or disable db triggers. DB triggers should also be disabled by default, and ahould have a separate set of pragmas to enable or disable them.
The main utility of connect triggers is to load extensions needed by, e.g., views and triggers, to create temp tables and triggers, and so on. That's too powerful to permit in untrusted DBs, which is why connection triggers must be disabled by default. The shell could warn of their presence too... Regarding savepoint and rollback to a savepoint, I'll have to think about that some more. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
