Hello, Has it ever been discussed (or for good reason never been considered) to extent the SAVEPOINT command with respect to its behavior if there is no enclosing transaction?
At the moment I am manually keeping track of enclosing transactions and then switch dynamically between "SAVEPOINT" and "BEGIN IMMEDIATE; SAVEPOINT" in order to start an immediate transaction. It seems to me that it would be a nice feature to have a "SAVEPOINT [name] [IMMEDIATE/DEFERRED/EXCLUSIVE]" command that obtains a lock of the given type if it is not within another BEGIN..COMMIT. Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
