From: Holger Jakobs <holger@jakobs.com>
To: JanWieck@Yahoo.com
Cc: sszabo@megazone.bigpanda.com
Cc: pgsql-sql@postgresql.org
Subject: Re: transaction processing after error in statement
Date: Tue, 11 Nov 2003 07:57:33 +0100 (CET)
Message-ID: <200311110658.hAB6wFJ25120@bg.bib.de> (raw)
In-Reply-To: <3FAFD756.2000704@Yahoo.com>
>
> Why is that "funny behaviour" for you? By putting the statements into
> a transaction block you told the data management system "I want this
> group of statements to be atomic". Atomic means all or nothing. It
> might not be exactly what you intended to say, and you have a point
> if you conclude that PostgreSQL is limited because it doesn't let you
> say anything in between all or nothing. But after all, thus far it is
> only doing what you asked for.
>
It is "funny behaviour", because I expect those operations of the
transaction, which executed successfully, to be performed in an atomic
way. It is obvious that I cannot expect an operation which reported an
error to have any effect.
"Atomic" means that all operations (whether successful or not) will be
carried out all together or none of them - but only the successful ones
will have had an effect.
Again: Why not make a difference between "commit" and "rollback" in a
transaction in this case? Why not let the user decide which parts should
be commited? The practical reason is that programming would become a lot
more convenient. (if there is a practical reason it does not necessarily
need a technical reason, I believe.)
Sincerely,
Holger
--
Holger@Jakobs.com, Bergisch Gladbach, Germany
Telefon (0 22 02) 5 99 91 oder (01 77) 7 92 24 66
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: holger@jakobs.com, JanWieck@Yahoo.com, sszabo@megazone.bigpanda.com
Subject: Re: transaction processing after error in statement
In-Reply-To: <200311110658.hAB6wFJ25120@bg.bib.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox