From 96d053c866000c8adda86926e7a821332c83f1a0 Mon Sep 17 00:00:00 2001 From: Martin Blech Date: Tue, 2 Dec 2014 17:30:46 -0300 Subject: [PATCH] Added ATOMIC_REQUESTS=True to default DB setup Quoting Two Scoops of Django: > Use `ATOMIC_REQUESTS` as long as the performance overhead is bearable. That > means "forever" on most sites. --- .../{{cookiecutter.repo_name}}/config/common.py | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/{{cookiecutter.repo_name}}/{{cookiecutter.repo_name}}/config/common.py b/{{cookiecutter.repo_name}}/{{cookiecutter.repo_name}}/config/common.py index deeff460..4f441d03 100644 --- a/{{cookiecutter.repo_name}}/{{cookiecutter.repo_name}}/config/common.py +++ b/{{cookiecutter.repo_name}}/{{cookiecutter.repo_name}}/config/common.py @@ -264,4 +264,8 @@ class Common(Configuration): } # END LOGGING CONFIGURATION + @classmethod + def post_setup(cls): + cls.DATABASES['default']['ATOMIC_REQUESTS'] = True + # Your common stuff: Below this line define 3rd party library settings