Ugh, of course, stupid mistake in explanation -
Of course it must be SAVEPOINT, not again BEGIN.
A) so to have:
BEGIN
SAVEPOINT A
...
RELEASE A
SAVEPOINT B
...
RELEASE B
...
COMMIT;
B) or to have:
BEGIN
SAVEPOINT A
...
SAVEPOINT B
...
RELEASE B
...
RELEASE A
COMMIT;
I realise both ways have code efficiency issues, but just is there a real
execution speed difference?
On 2013/06/08 16:20, Igor Tandetnik wrote:
On 6/8/2013 10:17 AM, RSmith wrote:
Could someone please shortly discuss performance considerations for
having nested Transactions vs. sequential transactions in SQLite.
There ain't no such thing as a nested transaction. The second BEGIN statement
will simply fail.
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
