Tom Lane wrote:
Lukas Kahwe Smith <[EMAIL PROTECTED]> writes:
Err, I think you misunderstood what I said. My implementation uses
SAVEPOINTs already. The point is having some API where you do not have
to care of you are already in a transaction or not.
It's not that hard, is it?
if (PQtransactionStatus(conn) == PQTRANS_IDLE)
PQexec(conn, "BEGIN");
else
PQexec(conn, "SAVEPOINT foo");
Its not exactly convenient either, especially in the case of modular
code that may be developed by different people. Anyways, like I said I
have a solution in my framework to make life of module developers
easier. Obviously proper nested transactions would be the ideal, but so
it goes. I was just throwing this out here when I saw Peter's comment.
regards,
Lukas
---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
