CODEWITHSUNDEEP
djangopostgresql
Ram Rachum
Ram Rachum

Reputation: 88718

Django+Postgres: "current transaction is aborted, commands ignored until end of transaction block"

I've started working on a Django/Postgres site. Sometimes I work in manage.py shell, and accidentally do some DB action that results in an error. Then I am unable to do any database action at all, because for any database action I try to do, I get the error:

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

My current workaround is to restart the shell, but I should find a way to fix this without abandoning my shell session.

(I've read this and this, but they don't give actionable instructions on what to do from the shell.)

Upvotes: 82

Views: 46888

Answers (13)

Larry Kooper
Larry Kooper

Reputation: 71

This issue for me occurred in the context of running tests. There is always some database error that causes the transaction to be aborted. In my case, the offending statement was within a try/except block, where the error was logged and not reraised, so the error message was suppressed. If you get the "current transaction is aborted, commands ignored until end of transaction block" message with no apparent reason, look for a SQL call in a try/except block, and temporarily remove the try/except.

Upvotes: 0

Elijah Baraza
Elijah Baraza

Reputation: 311

In my case it happened because I had a migration file that I had not applied to the database. I fixed it by doing python manage.py migrate(or python3 manage.py migrate)

Upvotes: 0

Ninoslav Meic
Ninoslav Meic

Reputation: 11

There are a lot of useful answers on this topic, but still it can be a challenge to figure out what is the root of the issue. Because of this, I will try to give just a little more context on how I was able to figure out the solution for my issue.

For Django specifically, you want to turn on logs for db queries and before the error is raised, you can find the query that is failing in the console. Run that query directly on db, and you will see what is wrong.

In my case, one column was missing in db, so after migration everything worked correctly.

I hope this will be helpful.

Upvotes: 1

Wolkenarchitekt
Wolkenarchitekt

Reputation: 21248

WARNING: the patch below can possibly cause transactions being left in an open state on the db (at least with postgres). Not 100% sure about that (and how to fix), but I highly suggest not doing the patch below on production databases.

As the accepted answer does not solve my problems - as soon as I get any DB error, I cannot do any new DB actions, even with a manual rollback - I came up with my own solution.

When I'm running the Django-shell, I patch Django to close the DB connection as soon as any errors occur. That way I don't ever have to think about rolling back transactions or handling the connection.

This is the code I'm loading at the beginning of my Django-shell-session:

from django import db
from django.db.backends.util import CursorDebugWrapper
old_execute = CursorDebugWrapper.execute
old_execute_many = CursorDebugWrapper.executemany

def execute_wrapper(*args, **kwargs):
    try:
        old_execute(*args, **kwargs)
    except Exception, ex:
        logger.error("Database error:\n%s" % ex)
        db.close_connection()

def execute_many_wrapper(*args, **kwargs):
    try:
        old_execute_many(*args, **kwargs)
    except Exception, ex:
        logger.error("Database error:\n%s" % ex)
        db.close_connection()

CursorDebugWrapper.execute = execute_wrapper
CursorDebugWrapper.executemany = execute_many_wrapper

Upvotes: 3

wieczorek1990
wieczorek1990

Reputation: 8104

For me it was a test database without migrations. I was using --keepdb for testing. Running it once without it fixed the error.

Upvotes: 3

Eldamir
Eldamir

Reputation: 10062

I got this error in Django 1.7. When I read in the documentation that

This problem cannot occur in Django’s default mode and atomic() handles it automatically.

I got a bit suspicious. The errors happened, when I tried running migrations. It turned out that some of my models had my_field = MyField(default=some_function). Having this function as a default for a field worked alright with sqlite and mysql (I had some import errors, but I managed to make it work), though it seems to not work for postgresql, and it broke the migrations to the point that I didn't event get a helpful error message, but instead the one from the questions title.

Upvotes: 0

Bill Huneke
Bill Huneke

Reputation: 1101

I add the following to my settings file, because I like the autocommit feature when I'm "playing around" but dont want it active when my site is running otherwise.

So to get autocommit just in shell, I do this little hack:

import sys
if 'shell' in sys.argv or sys.argv[0].endswith('pydevconsole.py'):
    DATABASES['default']['OPTIONS']['autocommit'] = True

NOTE: That second part is just because I work in PyCharm, which doesnt directly run manage.py

Upvotes: 0

Vsevolod Dyomkin
Vsevolod Dyomkin

Reputation: 9451

You can try this:

from django.db import connection
connection._rollback()

The more detailed discussion of This issue can be found here

Upvotes: 126

Jeff Sheffield
Jeff Sheffield

Reputation: 6316

If you are using a django version before 1.6 then you should use Christophe's excellent xact module.

xact is a recipe for handling transactions sensibly in Django applications on PostgreSQL.

Note: As of Django 1.6, the functionality of xact will be merged into the Django core as the atomic decorator. Code that uses xact should be able to be migrated to atomic with just a search-and-replace. atomic works on databases other than PostgreSQL, is thread-safe, and has other nice features; switch to it when you can!

Upvotes: 0

Artur Barseghyan
Artur Barseghyan

Reputation: 14262

If you happen to get such an error when running migrate (South), it can be that you have lots of changes in database schema and want to handle them all at once. Postgres is a bit nasty on that. What always works, is to break one big migration into smaller steps. Most likely, you're using a version control system.

  • Your current version
  • Commit n1
  • Commit n2
  • Commit n3
  • Commit n4 # db changes
  • Commit n5
  • Commit n6
  • Commit n7 # db changse
  • Commit n8
  • Commit n9 # db changes
  • Commit n10

So, having the situation described above, do as follows:

  • Checkout repository to "n4", then syncdb and migrate.
  • Checkout repository to "n7", then syncdb and migrate.
  • Checkout repository to "n10", then syncdb and migrate.

And you're done. :)

It should run flawlessly.

Upvotes: 0

Ignacio Pérez
Ignacio Pérez

Reputation: 672

Check this

The quick answer is usually to turn on database level autocommit by adding:

'OPTIONS': {'autocommit': True,}

To the database settings.

Upvotes: 13

yvess
yvess

Reputation: 2124

this happens to me sometimes, often it's the missing 

manage.py migrate

or 

manage.py syncdb

as mentioned also here

it also can happen the other way around, if you have a schemamigration pending from your models.py. With south you need to update the schema with.

manage.py schemamigration mymodel --auto

Upvotes: 34

Richard
Richard

Reputation: 1863

I had this error after restoring a backup to a totally empty DB. It went away after running: 

./manage syncdb

Maybe there were some internal models missing from the dump...

Upvotes: 3

Related Questions