Le 17 févr. 2013 à 19:31, Anssi Kääriäinen <anssi.kaariai...@thl.fi> a écrit :
> I am not yet convinced that poolers implemented inside Django core are > necessary. In case I wasn't clear enough — I agree that Django core shouldn't provide connection pooling, because it'll be simplistic and hamper innovation outside of Django. > I also do believe that persistent database connections are a good > idea. I don't yet believe the implementation must be in Django core... The goal of my proposal is to save the cost (in response time) of establishing the database connection, in vanilla Django, without compromising reliability. I'm trying to help people who aren't even aware of the problem :) The implementation is quite straightforward: https://github.com/django/django/pull/733 Everything is controlled by a per-connection max-age setting. It can be set to a low value on rarely used connections, so they get closed quickly, and are re-opened only when necessary. Why would this not belong in Django core -- besides historical reasons? -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
