On 4 Feb 2011, at 9:42am, Dan Kennedy wrote: > The problem is that the trigger version is creating a statement journal > for each INSERT statement. It doesn't *really* need to, as there is no > way that this statement/trigger can hit a constraint after modifying > any rows. However at the moment I think SQLite opens a statement > transaction for any statement that will fire one or more triggers.
I'm not quite up with the terminology but now I'm interested. First, do you feel that this behaviour is a bug and can be addressed in future versions ? Second, is this the same as the automatic creation of transactions if the programmer doesn't create a transaction ? In other words, if the programmer doesn't do a BEGIN, does SQLite make one transaction for the INSERT, and another for each action inside anything that triggers ? Or do all the actions triggered by the INSERT get included within the same automatic transaction ? Simon. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
