I get the point that transactions can be nested and i am assuming
the begin transaction trigger only happens at the outer most transaction.
It still is the logical envelope which will be rolled back on a default abort.
(yes, i know one can back off to a save point).
Store a value... I don't know when a transaction begins or ends, and I
don't have a model of my own transaction. If i did, this conversation is moot.
thanks
brs
----- Original Message ----
From: Simon Slavin <slav...@bigfraud.org>
To: General Discussion of SQLite Database <sqlite-users@sqlite.org>
Sent: Wed, June 23, 2010 9:30:25 AM
Subject: Re: [sqlite] marking transaction boundaries
On 23 Jun 2010, at 5:19pm, b s wrote:
> I don't know when transaction
> begins or ends!
You are still ignoring the fact that transactions can be nested. One specific
INSERT command might be a member of three different transactions. Your model
allows only for one transaction per command.
If you have your own model of transactions, just do it all with triggers: store
a value somewhere for which transaction you're on, and have the triggers copy
this value and put it into your log.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
