On Fri, 2004-07-09 at 20:34, Bruce Momjian wrote:
Alvaro Herrera wrote:
Simon posted it. It is called RELEASE:
BEGIN;
SAVEPOINT x1;
INSERT INTO ...;
RELEASE SAVEPOINT x1;
SAVEPOINT x1;
INSERT INTO ...;
RELEASE SAVEPOINT x1;
SAVEPOINT x1;
INSERT INTO ...;
RELEASE SAVEPOINT x1;
Alvaro Herrera wrote:
On Fri, Jul 09, 2004 at 09:07:58PM +0200, Dennis Bjorklund wrote:
What is it?On Fri, 9 Jul 2004, Alvaro Herrera wrote:
Clearly savepoints do not allow for a snapshot to be released; nested
xacts do.
Why not?Clearly savepoints do not allow for a snapshot to be released; nested
xacts do.
Simon posted it. It is called RELEASE:
BEGIN;
SAVEPOINT x1;
INSERT INTO ...;
RELEASE SAVEPOINT x1;
SAVEPOINT x1;
INSERT INTO ...;
RELEASE SAVEPOINT x1;
SAVEPOINT x1;
INSERT INTO ...;
RELEASE SAVEPOINT x1;
Oracle uses ROLLBACK TO SAVEPOINT...identical pretty much.
Oracle's support of autonomous transactions looks to be identical to
nested transactions (Alvaro's advice required there...). They don't
allow you to explicitly call them, but you can use BEGIN/COMMIT in a
host program that calls a stored procedure, which also contains
BEGIN/COMMIT, effectively giving nested txns.
(...hopefully clearing up any discussion on "intermediate commits"
whoever mentioned those...)
Best regards, Simon Riggs
