Re: current transaction is aborted, commands ignored until end of transaction block

Hi Andreas,

The reason that you are seeing this likely is because of a bug in the way django handled Postgres autocommit. This has been documented here: https://docs.djangoproject.com/en/dev/releases/1.5/#behavior-of-autocommit-database-option-on-postgresql-changed

Regards,

Ryan

On Friday, May 24, 2013 1:55:57 AM UTC-7, Andréas Kühne wrote:

Hi all,

I am working on upgrading our system from django 1.3.1 to django 1.5.1, and have run into a huge problem. The site we are running has multilingual support and the platform has multiple top level domain sites connected to it. Running locally on my machine I get an error when I try to switch languages. 

The error is : "current transaction is aborted, commands ignored until end of transaction block", so I guess that something is not being commited correctly to the database. If i change the database setttings to "autocommit = True" then the site works perfectly. It doesn't matter which page I go to, when there is a database lookup it will not work. It does work in english (default language) and oddly enough swedish (can be because that is "our" language, which I test first).

I was wondering if there is anyone out there that has any ideas why a change from 1.3.1 to 1.5.1 would result in these errors or if anyone has any suggestions on what this could be?

Regards,

Andréas

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.