RE: Transaction problems with large objects in PgSQLpy
"Pinchart, Laurent" <[email protected]> Fri, 13 Jun 2003 09:45:54 +0200
| Newsgroups | gmane.comp.python.db.pypgsql.user |
|---|---|
| Message-ID | <[email protected]> |
> In regards to the problem in Connection.binary, which commits a transaction > if it has started one, but doesn't reset the "inTransaction" flag to 0: > > After some thought, I now believe that the transaction should not be committed > after the large object is created. This would push the responsibility of commiting > the transactiont to the application programmer. The sequence would usually be: I agree Laurent Pinchart ------------------------------------------------------- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5