Autocommit Migration from Django 1.7 to 1.8

--------------------------------------------------
Hire the world's top talent on demand or became one of them at Toptal: https://topt.al/25cXVn
and get $2,000 discount on your first invoice
--------------------------------------------------

Take control of your privacy with Proton's trusted, Swiss-based, secure services.
Choose what you need and safeguard your digital life:
Mail: https://go.getproton.me/SH1CU
VPN: https://go.getproton.me/SH1DI
Password Manager: https://go.getproton.me/SH1DJ
Drive: https://go.getproton.me/SH1CT

Music by Eric Matyas
https://www.soundimage.org
Track title: Light Drops

--

Chapters
00:00 Autocommit Migration From Django 1.7 To 1.8
02:08 Accepted Answer Score 14
02:50 Thank you

--

Full question
https://stackoverflow.com/questions/2944...

--

Content licensed under CC BY-SA
https://meta.stackexchange.com/help/lice...

--

Tags
#python #django

#avk47

ACCEPTED ANSWER

Score 14

The following was outlined in the Django 1.7 Databases docs:

In previous versions of Django, database-level autocommit could be enabled by setting the autocommit key in the OPTIONS part of your database configuration in DATABASES.

Since Django 1.6, autocommit is turned on by default. This configuration is ignored and can be safely removed.

And as per the 1.8 Release Notes, this feature was removed.

If you still want to keep the setting for some reason, simply move it out of OPTIONS:

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.postgresql_psycopg2',
        'HOST': 'localhost',
        'PORT': '5432',
        'NAME': 'bp_django_auth',
        'USER': 'postgres',
        'PASSWORD': 'abcd1234',
        'AUTOCOMMIT': True,
    }
}