diff options
| author | Anssi Kääriäinen <akaariai@gmail.com> | 2012-05-26 23:19:13 +0300 |
|---|---|---|
| committer | Anssi Kääriäinen <akaariai@gmail.com> | 2012-07-01 19:36:43 +0300 |
| commit | f572ee0c65ec5eac9edb0cb3e35c96ec86d89ffb (patch) | |
| tree | f2b3ebd0d6df09cdf29b6c9e10ee0e5210e44ee8 /docs | |
| parent | da573fbb4172fb962c9f021fc0c03cf91b13e746 (diff) | |
Fixed #16047 -- Restore autocommit state correctly on psycopg2
When the postgresql_psycopg2 backend was used with DB-level autocommit
mode enabled, after entering transaction management and then leaving
it, the isolation level was never set back to autocommit mode.
Thanks brodie for report and working on this issue.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/releases/1.5.txt | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/docs/releases/1.5.txt b/docs/releases/1.5.txt index 2f20f5f9f9..4544be0eac 100644 --- a/docs/releases/1.5.txt +++ b/docs/releases/1.5.txt @@ -168,6 +168,15 @@ number was inside the existing page range. It does check it now and raises an :exc:`InvalidPage` exception when the number is either too low or too high. +Behavior of autocommit database option on PostgreSQL changed +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +PostgreSQL's autocommit option didn't work as advertised previously. It did +work for single transaction block, but after the first block was left the +autocommit behavior was never restored. This bug is now fixed in 1.5. While +this is only a bug fix, it is worth checking your applications behavior if +you are using PostgreSQL together with the autocommit option. + Features deprecated in 1.5 ========================== |