connections (CONN_MAX_AGE = 0) and switching settings.DATABASE["default"] in a middleware at the beginning of every request. Modifying settings at runtime isn'

type of CONN_MAX_AGE database option. https://github.com/django/django/pull/12631 - Fixed #31404 -- Changed selector-chosen's multiple attribute to HTML5 boolean syntax

connections with CONN_MAX_AGE = 0 but the performance hit is likely not worth the reliability improvement. On the ticket you say that you're seeing "a number of requests

connections if CONN_MAX_AGE >> was set to None? Could have sworn it was that way for a while? >> >> In any case, I just tried the Javascript & CSS Makefile with

f = Food.objects.get(id=2) f.weight= {'0.5': '0.5kg - 1kg'} f.save() Save model by code then OK. But I can't save model in admin.

using `CONN_MAX_AGE`, then there's a huge benefit. > > The only issue I can see is that it only improves performance if you've > got memcached installed. That's

value for CONN_MAX_AGE. > > > Since I committed the patch, I discovered that persistent connections don't interact well with runserver. > > By default, the development

**tl;dr** I believe that persistent database connections are a good idea. Please prove me wrong :) --