From: | mikie <mikie(dot)pl(at)gmail(dot)com> |
---|---|
To: | pgsql-php(at)postgresql(dot)org |
Subject: | Re: transactions from PHP - double COMMIT required? |
Date: | 2007-03-05 09:30:03 |
Message-ID: | ca35ce500703050130g46db55f1r23e2ef96fd8b18e7@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-php |
2007/3/2, Martin Marques <martin(at)bugs(dot)unl(dot)edu(dot)ar>:
> mikie wrote:
> > 2007/3/1, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>:
> >> Yeah, do the above recommendation to see if all of your statements are
> >> making
> >> thier way into pg
> >
> > OK, I have checked the logs. I can see both COMMIT statements in the
> > log - the first commit from my transaction and then the other that I
> > send to workaround the problem.
>
> There must be some other problem. Do you have trasaction ID on the logs?
> See if both commits go in the same transaction.
Could you please advise me how to check the transaction ID in the log?
> Any errors during the transaction?
As I wrote in my first post, I make this error intentionally to check
if transaction works (if something fails, then the entire transaction
should be rolled back). I intentionally give wrong data in the "date"
field for example.
Perhaps I should ask again: is it my responsibility to check if the
transaction failed and issue a ROLLBACK command, or will the PG server
do it automatically?
From | Date | Subject | |
---|---|---|---|
Next Message | Martin Marques | 2007-03-05 11:56:11 | Re: transactions from PHP - double COMMIT required? |
Previous Message | Martin Marques | 2007-03-02 12:51:17 | Re: transactions from PHP - double COMMIT required? |