On Wed, Oct 19, 2011 at 6:50 PM, Marko Kreen <markokr(at)gmail(dot)com> wrote:
> Let's clarify that further - DB-API *MUST* say that .close()
> [and also .__del__()] will rollback. Eg - imagine
> driver accessing .dbf / .csv files directly.
> But there is no good reason to require communication
> with backend if the backend will rollback anyway
> on connection close.
Yes, this is our current position. Changing from it could only improve
the interaction between "sloppy code" and middleware, and as you have
pointed out this would make edge case more troublesome.
Thank you for the discussion, I wanted to hear the opinion of somebody
on the other side of the socket :)
In response to
psycopg by date
|Next:||From: Frank Kauff||Date: 2011-10-19 19:35:45|
|Subject: Re: Error: no Python Codec for client encoding|
|Previous:||From: Marko Kreen||Date: 2011-10-19 17:50:15|
|Subject: Re: Rollback on close [Was: Fwd: [DB-SIG] conn.close() idempotence]|