On Fri, Feb 17, 2012 at 9:58 PM, Florian Apolloner <[email protected]>wrote:
> > > On Friday, February 17, 2012 10:11:57 PM UTC+1, Cal Leeming [Simplicity > Media Ltd] wrote: >> >> # Apparently this will stop many connections to MySQL >> from django.core import signals >> from django.db import close_connection >> signals.request_finished.**disconnect(close_connection) >> > > This approach has quite a few issues on it's own, eg for postgres if the > transaction is broken all following requests will raise a 500. You have to > at least reset the connection state to something useable again. > Could you elaborate on this a bit more? And would this affect MySQL? > > I'd love to see this as a 'settings.py' option, does anyone else think >> this would be a good idea?? Something like 'persistent' : True.. maybe? >> > > -1, we already have enough of them ;) > Hmm - what about a documentation update, so at least people in the future don't have to go trawling through tons of mailing lists to find this. > > Cheers, > Florian > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-developers/-/pBSx93aPffIJ. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
