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

2013/5/30 Sam Solomon > Hmm, yeah, Ryan could be onto something, but that doesn't really help > figure out the root cause (which likely was an error that existing before > upgrading but just went ignored). > > What should help get to the root issue is checking out the postgresql log > file (for m

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

Hmm, yeah, Ryan could be onto something, but that doesn't really help figure out the root cause (which likely was an error that existing before upgrading but just went ignored). What should help get to the root issue is checking out the postgresql log file (for me: /var/log/postgresql/postgresq

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, M

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

Hi The easiest way to finding the causing error in my opinion is to execute the generated queries by hand in a psql shell. Normally I had a mismatch between model definitions and table layouts in the database. But at the end I also had a logical error with handling the transactions in the code.

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

Hi Andreas, > The error is : "current transaction is aborted, commands ignored until end > of transaction block", I guess you use postgres. This is a standard error that postgres thows if you do any database action in a transaction after any other error. You need to find the previous error that