On Fri, Jul 24, 2009 at 8:17 PM, James Bennett<ubernost...@gmail.com> wrote: > 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.
There are lots of requests for ways to build specific types of queries, too. You can't really commit a QuerySet method for one thing and then... Anyway, even if I was to put together a patch for this, it wouldn't be for quite a while--not until after I've tested and used it in production for quite a while, done more extensive benchmarking, and in any case I wouldn't submit anything but bug reports right now with the tracker so (understandably) backlogged from the release freeze. So relax, I'm not jumping head-first into this. -- Glenn Maynard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
