Databases
StackOverflow2013
Postsdbo
PODjango 1.6 TransactionManagementError: database doesn't behave properly when autocommit is off
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODjango 1.6 TransactionManagementError: database doesn't behave properly when autocommit is off
    primarykey
    data
    text
    <p>I'm trying to update a project from Django 1.5.5 to Django 1.6 however I've been getting this error everywhere.</p> <pre class="lang-py prettyprint-override"><code>Traceback (most recent call last): File "project/virtualenv/lib/python2.7/site-packages/django/core/handlers/base.py", line 114, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "project/virtualenv/lib/python2.7/site-packages/django/contrib/admin/sites.py", line 215, in wrapper return self.admin_view(view, cacheable)(*args, **kwargs) File "project/virtualenv/lib/python2.7/site-packages/django/utils/decorators.py", line 99, in _wrapped_view response = view_func(request, *args, **kwargs) File "project/virtualenv/lib/python2.7/site-packages/django/views/decorators/cache.py", line 52, in _wrapped_view_func response = view_func(request, *args, **kwargs) File "project/virtualenv/lib/python2.7/site-packages/django/contrib/admin/sites.py", line 197, in inner return self.login(request) File "project/virtualenv/lib/python2.7/site-packages/django/views/decorators/cache.py", line 52, in _wrapped_view_func response = view_func(request, *args, **kwargs) File "project/virtualenv/lib/python2.7/site-packages/django/contrib/admin/sites.py", line 330, in login return login(request, **defaults) File "project/virtualenv/lib/python2.7/site-packages/django/views/decorators/debug.py", line 75, in sensitive_post_parameters_wrapper return view(request, *args, **kwargs) File "project/virtualenv/lib/python2.7/site-packages/django/utils/decorators.py", line 99, in _wrapped_view response = view_func(request, *args, **kwargs) File "project/virtualenv/lib/python2.7/site-packages/django/views/decorators/cache.py", line 52, in _wrapped_view_func response = view_func(request, *args, **kwargs) File "project/virtualenv/lib/python2.7/site-packages/django/contrib/auth/views.py", line 43, in login auth_login(request, form.get_user()) File "project/virtualenv/lib/python2.7/site-packages/django/contrib/auth/__init__.py", line 83, in login request.session.cycle_key() File "project/virtualenv/lib/python2.7/site-packages/django/contrib/sessions/backends/base.py", line 277, in cycle_key self.create() File "project/virtualenv/lib/python2.7/site-packages/django/contrib/sessions/backends/db.py", line 40, in create self.save(must_create=True) File "project/virtualenv/lib/python2.7/site-packages/django/contrib/sessions/backends/db.py", line 62, in save with transaction.atomic(using=using): File "project/virtualenv/lib/python2.7/site-packages/django/db/transaction.py", line 244, in __enter__ "Your database backend doesn't behave properly when " TransactionManagementError: Your database backend doesn't behave properly when autocommit is off. Turn it on before using 'atomic'. </code></pre> <p>I've removed <code>TransactionMiddleware</code> from <code>MIDDLEWARE_CLASSES</code> and replaced it with <code>ATOMIC_REQUESTS = True</code>. (Same error even if I don't do this step)</p> <p>Can someone please shed some light on this?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USSunnySydeUp
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODjango 1.6 TransactionManagementError: database doesn't behave properly when autocommit is off
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODjango 1.6 TransactionManagementError: database doesn't behave properly when autocommit is off
      1. USuser3019587
      1. VTFavorite
    3. VO
      singulars
      1. PODjango 1.6 TransactionManagementError: database doesn't behave properly when autocommit is off
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAre you trying to use a command that uses an atomic save (ie, get_or_create()), within a code block that has been decorated with a @transaction
      singulars
      1. PODjango 1.6 TransactionManagementError: database doesn't behave properly when autocommit is off
      1. USOldTinfoil
    2. COI'm just using Django's generic views and doing get_or_create in south datamigrations. I haven't explicitly decorated any views with @transaction myself, but I'm not sure if Django automatically does this. Even so, Django still throws the same error when doing the datamigration.
      singulars
      1. PODjango 1.6 TransactionManagementError: database doesn't behave properly when autocommit is off
      1. USSunnySydeUp
    3. COHow are you using get_and_create() within the South Migrations? I pretty sure South uses @transactions for optimisation (if it doesn't, I'd be very surprised). If you replace the get_or_create() with the full expanded definition (ie, the try/catch block) and that should play nicely...
      singulars
      1. PODjango 1.6 TransactionManagementError: database doesn't behave properly when autocommit is off
      1. USOldTinfoil
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload