| From: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
|---|---|
| To: | Julian <tempura(at)internode(dot)on(dot)net> |
| Cc: | "psycopg(at)postgresql(dot)org" <psycopg(at)postgresql(dot)org> |
| Subject: | Re: Psycopg 2.5 released |
| Date: | 2013-04-08 07:04:36 |
| Message-ID: | CA+mi_8ZKBeLzvqZghdue41BcRarDBHkVKGa9PwmWVsJk-TBcUQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | psycopg |
On Mon, Apr 8, 2013 at 1:57 AM, Julian <tempura(at)internode(dot)on(dot)net> wrote:
> Hi,
> Just an observation on your sites release notes:
>
> "when the connection block exits normally the current transaction is
> committed, if it exits with an exception instead the transaction is
> rolled back, *in either case the connection is closed*."
>
> Its not what I prefer, I went and checked anyway and it appears it
> doesn't (close the connection for either commit or rollback).
I think you are right: the connection is *NOT* closed after the with
block. Will fix the article, thank you very much.
-- Daniele
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael van Tellingen | 2013-04-09 06:59:34 | Re: Psycopg 2.5 released |
| Previous Message | Julian | 2013-04-08 07:01:05 | Best practice for managing connections? |