From: Martin Marques <martin@bugs.unl.edu.ar>
To: mikie <mikie.pl@gmail.com>
Cc: pgsql-php@postgresql.org
Subject: Re: transactions from PHP - double COMMIT required?
Date: Thu, 1 Mar 2007 09:47:22 -0300 (ART)
Message-ID: <Pine.LNX.4.64.0703010947070.606@bugs.unl.edu.ar> (raw)
In-Reply-To: <ca35ce500703010329j329b8a5h6ee8958ddb6711e0@mail.gmail.com>
References: <ca35ce500703010306nd06dcfcy1247fb2b4297b0c2@mail.gmail.com>
<20070301131523.fgfm83nb9y2kgo4c@imp3.uta.fi>
<ca35ce500703010329j329b8a5h6ee8958ddb6711e0@mail.gmail.com>
On Thu, 1 Mar 2007, mikie wrote:
>
> Now, when I try to do some inserts within my transaction I don't know if
> they will fail or not. Eitherway I am closing my transaction with the
> COMMIT; command - is that correct way ?
Yes.
--
21:50:04 up 2 days, 9:07, 0 users, load average: 0.92, 0.37, 0.18
---------------------------------------------------------
Lic. Martín Marqués | SELECT 'mmarques' ||
Centro de Telemática | '@' || 'unl.edu.ar';
Universidad Nacional | DBA, Programador,
del Litoral | Administrador
---------------------------------------------------------
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: martin@bugs.unl.edu.ar, mikie.pl@gmail.com
Subject: Re: transactions from PHP - double COMMIT required?
In-Reply-To: <Pine.LNX.4.64.0703010947070.606@bugs.unl.edu.ar>
References: <ca35ce500703010306nd06dcfcy1247fb2b4297b0c2@mail.gmail.com> <20070301131523.fgfm83nb9y2kgo4c@imp3.uta.fi> <ca35ce500703010329j329b8a5h6ee8958ddb6711e0@mail.gmail.com> <Pine.LNX.4.64.0703010947070.606@bugs.unl.edu.ar>
* 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