Re: transactions from PHP - double COMMIT required?

The client must issue a command to commit or rollback the transaction.

In your example, are you sending all of the SQL lines (including the
COMMIT) as a single execution? It sounds like the interface stops
executing as soon as an error is reached. So perhaps change your code
to execute the COMMIT separately after all the other commands have
executed.

John




On Mar 1, 2007, at 7:45 AM, mikie wrote:

> Yes, that is nice way to work with databases, but I am on PHP4 and I
> am not using the PDO.
> 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?



John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL