Skip site navigation (1) Skip section navigation (2)

Re: autocommit and Django

From: Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>
To: Federico Di Gregorio <federico(dot)digregorio(at)dndg(dot)it>
Cc: psycopg(at)postgresql(dot)org
Subject: Re: autocommit and Django
Date: 2011-06-14 10:23:18
Message-ID: BANLkTi=6tOcCy812_GKsXM8Bx_FD=UUoOA@mail.gmail.com (view raw or flat)
Thread:
Lists: psycopg
On Tue, Jun 14, 2011 at 11:02 AM, Federico Di Gregorio
<federico(dot)digregorio(at)dndg(dot)it> wrote:

> If we don't want to wait for the #(at)§%£$! person that wrote the Django
> code to fix it we can just make .autocommit a real attribute and set the
> session autocommit mode when it is assigned True/False.

This wouldn't work as if the exception is raised it means that they
have already started a transaction, probably by setting time_zone to
chicago or something like that. The "create database" they mean to run
outside the transaction is then doomed to fail.

-- Daniele

In response to

psycopg by date

Next:From: W. Matthew WilsonDate: 2011-06-19 15:21:09
Subject: Can I map "raise XXX" to some custom python exceptions?
Previous:From: Karsten HilbertDate: 2011-06-14 10:15:39
Subject: Re: autocommit and Django

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group