From: jose soares <jose@sferacarta.com>
Cc: hackers postgres <pgsql-hackers@postgresql.org>
Subject: TRANSACTION "WARNINGS"
Date: Wed, 01 Dec 1999 11:53:15 +0100
Message-ID: <3844FE1A.9E48AF93@sferacarta.com> (raw)
References: <199909170445.AAA07310@candle.pha.pa.us>
Hi all,
I have again a problem about TRANSACTIONS.
I had some answers about this matter some time ago, but unfortunately the solution wasn't yet found.
Transaction are essentials for a relational database but in the case of PostgreSQL some times it's
impossible
to use them. Right now I'm in a middle of a work and I need to use transactions but I can't go on because
there are some "warnings" that I would like to avoid but I can't.
Problem:
PostgreSQL automatically ABORTS at every error, even a syntax error.
I know that a transaction is a sequence of operations which either all succeed, or all fail, and
this behavior is correct for batch mode operations, but it is not useful in interactive mode where
the user
could decide if the transaction should be COMMITed or ROLLBACKed even in presence of errors.
Other databases have such behavior.
What about to have a variable to set like:
SET TRANSACTION MODE TO {BATCH | INTERACTIVE}
where:
BATCH: the transaction ROLLBACK at first error and COMMIT only if all operations
succeed.
INTERACTIVE: leaves the final decision to user to COMMIT or ROLLBACK even if some error occurred.
Comments...
Jose'
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-interfaces@postgresql.org
Cc: jose@sferacarta.com, pgsql-hackers@postgresql.org
Subject: Re: TRANSACTION "WARNINGS"
In-Reply-To: <3844FE1A.9E48AF93@sferacarta.com>
* 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