Expand on autocommit setting for Django 1.6 about django-pyodbc HOT 6 CLOSED

Interesting. Besides syncdb, what other ramifications does this change have?

from django-pyodbc.

Good question; I'm not 100% sure about all of it. I just had a skim through a couple of management commands (eg, loaddata as well), but I can't actually see how it works. They call transaction.commit_unless_managed(), but I don't otherwise see where it would get committed! (I did a quick test with 1.5, and even explicitly setting autocommit to False syncdb will still create tables). I think I've just confused myself.

from django-pyodbc.

I think I'm having this exact issue. Everything worked great for me under 1.5 (and django-pyodbc 0.2). But after upgrading to 1.6 and 0.2.3, it's all gone to crap. syncdb looks like its doing fine. But no tables created. Was there a quick fix with a setting somewhere?

from django-pyodbc.

@8one6 I'm relying on my notes now because I haven't touched that in a while (and I switched to using django-pyodbc-azure for our purposes anyway), but I think adding

    'OPTIONS': {
        'autocommit': True
    }

should be enough.

from django-pyodbc.

Which version of Django are you using? Out of curiosity, why the switch to django-pyodbc-azure? I'm mostly trying to sort out the pros and cons of various approaches for getting things to work smoothly with multiple databases.

from django-pyodbc.

I was using Django 1.6.

I was writing a geodjango driver for SQL Server, and wanted to support SQL Azure as well -- plus the autocommit issue I discovered here and django-pyodbc-azure just worked for my particular configuration. It was a little while ago so I don't recall any other details, I'm sorry.

from django-pyodbc.