pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: David Legault <legault.david@gmail.com>
To: mikie <mikie.pl@gmail.com>
Cc: pgsql-php@postgresql.org
Subject: Re: transactions from PHP - double COMMIT required?
Date: Thu, 1 Mar 2007 08:16:53 -0500
Message-ID: <e0b20d410703010516l20edae05oc2a718d4c970fcb5@mail.gmail.com> (raw)
In-Reply-To: <ca35ce500703010502j77327b1bn9ca679e9dea38df9@mail.gmail.com>
References: <ca35ce500703010306nd06dcfcy1247fb2b4297b0c2@mail.gmail.com>
	<20070301131523.fgfm83nb9y2kgo4c@imp3.uta.fi>
	<ca35ce500703010329j329b8a5h6ee8958ddb6711e0@mail.gmail.com>
	<e0b20d410703010418m3f931527wb2e81e3f3ab0c9f4@mail.gmail.com>
	<ca35ce500703010445n67ca6714id0b10b393859f8e0@mail.gmail.com>
	<Pine.LNX.4.64.0703010948200.606@bugs.unl.edu.ar>
	<ca35ce500703010502j77327b1bn9ca679e9dea38df9@mail.gmail.com>

Probably because the pgsql extension in PHP has an internal representation
that doesn't fit with what the DB does (auto rollback on error).

it keeps a state of transaction flag as active even though the DB rolled
back when the error occured thus flagging an error when you want to start
another one or execute another query.

BEGIN

Queries

check for error (pg_last_error) after each query, if error, rollback and
exit transaction "block"

COMMIT (no errors found)

The best would be to enclose the query in a function so that you can "exit"
the block with a return statement or some similar construct. I can't
remember if PHP supports block definition like in C

{
 // group
 // of
 // calls
 // block
}

David

On 3/1/07, mikie <mikie.pl@gmail.com> wrote:
>
> > > But getting back to my problem - perhaps there is something I
> > > misunderstood: is it the client application responsibility to check if
> > > the transaction failed or succeeded and issue COMMIT or ROLLBACK
> > > accordingly (how do I close the transaction block in that case)?
> > > Or is it the database server that is suppose to check if transaction
> > > succeded and perform the query, or ROLLBACK if anything went wrong?
> >
> > PG will rollback all transactions that have an error in some part, as it
> > can't commit the transaction as a whole.
>
> OK, so my way of programming seems correct.
> Then why do I have to send another COMMIT after failed transaction to
> continue with next queries in the same php script ?
>
> --
> Mike
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>

view thread (23+ messages)  latest in thread

Message-ID: <e0b20d410703010516l20edae05oc2a718d4c970fcb5@mail.gmail.com>
Permalink:  ../e0b20d410703010516l20edae05oc2a718d4c970fcb5@mail.gmail.com/
Also on:    postgresql.org/message-id/e0b20d410703010516l20edae05oc2a718d4c970fcb5@mail.gmail.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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: legault.david@gmail.com, mikie.pl@gmail.com
  Subject: Re: transactions from PHP - double COMMIT required?
  In-Reply-To: <e0b20d410703010516l20edae05oc2a718d4c970fcb5@mail.gmail.com>
  References: <ca35ce500703010306nd06dcfcy1247fb2b4297b0c2@mail.gmail.com> <20070301131523.fgfm83nb9y2kgo4c@imp3.uta.fi> <ca35ce500703010329j329b8a5h6ee8958ddb6711e0@mail.gmail.com> <e0b20d410703010418m3f931527wb2e81e3f3ab0c9f4@mail.gmail.com> <ca35ce500703010445n67ca6714id0b10b393859f8e0@mail.gmail.com> <Pine.LNX.4.64.0703010948200.606@bugs.unl.edu.ar> <ca35ce500703010502j77327b1bn9ca679e9dea38df9@mail.gmail.com> <e0b20d410703010516l20edae05oc2a718d4c970fcb5@mail.gmail.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