On May 21, 2006, at 8:55 AM, Nick Hristov wrote:
line 35, in cursor
cursor.execute("SET TIME ZONE %s", [TIME_ZONE])
ProgrammingError: ERROR: current transaction is aborted, commands
ignored until end of transaction block
SET TIME ZONE 'GMT'
# Wtf? I guess a transaction was opened in the previous save and
it was
not closed, so all of my following db queries are going to fail
too? To
some degree that sounds fine, I guess... it is fail safe. But how
do I
now abort the current transaction and start a fresh?
# Or do my saves get batched and executed as a transaction? Given the
previous save did not work, it should not be batched...
This is a known problem and is related to Postgres transactions, see
below for a fix (update to magic removal)
or you can catch exceptions and roll them back yourself:
http://code.djangoproject.com/ticket/852
Don
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.54.131.8 with SMTP id e8mr173081wrd;
Sun, 21 May 2006 10:56:27 -0700 (PDT)
Return-Path: <[EMAIL PROTECTED]>
Received: from smtp3.pacifier.net (smtp3.pacifier.net [64.255.237.173])
by mx.googlegroups.com with ESMTP id v11si719498cwb.2006.05.21.10.56.26;
Sun, 21 May 2006 10:56:27 -0700 (PDT)
Received-SPF: neutral (googlegroups.com: 64.255.237.173 is neither permitted
nor denied by best guess record for domain of [EMAIL PROTECTED])
Received: from [192.168.0.2] (ip240.wcsm-250.dsl-acs2.sea.iinet.com
[207.202.250.240])
by smtp3.pacifier.net (Postfix) with ESMTP id 37432827EB
for <django-users@googlegroups.com>; Sun, 21 May 2006 10:56:26 -0700
(PDT)
Mime-Version: 1.0
Content-Type: text/plain
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PROTECTED]>
From: Don Arbow <[EMAIL PROTECTED]>
Subject: Re: noobie db problems
Date: Sun, 21 May 2006 10:56:26 -0700
To: django-users@googlegroups.com
X-Mailer: Apple Mail (2.746.2)
On May 21, 2006, at 8:55 AM, Nick Hristov wrote:
line 35, in cursor
cursor.execute("SET TIME ZONE %s", [TIME_ZONE])
ProgrammingError: ERROR: current transaction is aborted, commands
ignored until end of transaction block
SET TIME ZONE 'GMT'
# Wtf? I guess a transaction was opened in the previous save and
it was
not closed, so all of my following db queries are going to fail
too? To
some degree that sounds fine, I guess... it is fail safe. But how
do I
now abort the current transaction and start a fresh?
# Or do my saves get batched and executed as a transaction? Given the
previous save did not work, it should not be batched...
This is a known problem and is related to Postgres transactions, see
below for a fix (update to magic removal)
or you can catch exceptions and roll them back yourself:
http://code.djangoproject.com/ticket/852
Don
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
