On Fri, Jul 24, 2009 at 7:03 PM, Glenn Maynard<[email protected]> wrote: > What I need is sensible, simple and faster, but since someone else > might want to turn it into something complex and unnecessary, it > shouldn't be done?
While the specific thing you personally are asking for might not be that much, we can't really commit it to Django and then say "Hey, we only did this for Glenn and nobody else gets to ask for features building on it". And since there have already been multiple requests for Django to grow full-blown connection-pooling utilities, I feel pretty confident that's where it would end up. If you don't like it, simply detach the signal handler that closes the connection (and register your own handler that resets the connection). But Django itself shouldn't add that because it really throws open a Pandora's box of things which shouldn't be in Django but which will be demanded anyway. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
