pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ed Loehr <eloehr@austin.rr.com>
To: Manuel Lemos <mlemos@acm.org>
Cc: lylyeoh@mecomb.com
Cc: tomg@admin.nrnet.org
Cc: pgsql-general@postgresql.org
Subject: Re: Connecting website with SQL-database.....
Date: Tue, 25 Apr 2000 09:54:08 -0500
Message-ID: <3905B190.F575D31C@austin.rr.com> (raw)
References: <1315.150T22T2112775mlemos@acm.org>

Manuel Lemos wrote:
> 
> >> >Plus if you get a warning/error, Postgresql _requires_ you to rollback,
> >> >whereas many other databases don't.
> >>
> >> That's what Metabase expects. When there is an error, you should rollback
> >> before exiting a transaction with AutoCommit(Off).
> >>
> >> I noticed the discussion but I could not quite figure what was the problem.
> 
> >The problem on this, from my perspective, is that if you have a transaction
> >that consists of 20 queries, and the 14th query fails, then you'd like to
> >be able to abort only the *statement*, recovering in the client application
> >in whatever way seems appropriate.  Automatically *forcing* a rollback
> >takes that recovery choice away.
> 
> The problem is that PostgreSQL lacks of transactions check points with which
> you could do what you want.  That doesn't mean that transactions work
> differently from other DBMS.  There's just only one check point to rollback:
> the transaction begining.

I think the difference with other RDBMS that I and several others were
highlighting was the *behavior* resulting from a failed statement within a
transaction (i.e., aborted transaction vs. aborted statement), but I think
your orthogonal point is still valid.

Regards,
Ed Loehr



view thread (18+ messages)

Message-ID: <3905B190.F575D31C@austin.rr.com>
Permalink:  ../3905B190.F575D31C@austin.rr.com/
Also on:    postgresql.org/message-id/3905B190.F575D31C@austin.rr.com

 · 

reply

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: eloehr@austin.rr.com, mlemos@acm.org, lylyeoh@mecomb.com, tomg@admin.nrnet.org, pgsql-general@postgresql.org
  Subject: Re: Connecting website with SQL-database.....
  In-Reply-To: <3905B190.F575D31C@austin.rr.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