Kevin Menard wrote: > I've experienced the exact opposite. When I can say in a config file > that I want 10 connections in a pool, that's a lot easier for me than > setting up an external utility.
In my experience such simple behavior is rarely needed. When you actually need a pool it means that your app become pretty large so it requires not only static pool but also other settings like minimum spare connections, maximum spare connections, keep-alive timeouts etc... So this becomes a complex matter in itself and I'd rather Django not to reinvent this. For me this is very similar to the recommendation to use memcached as a cache backend instead of mimicking its rich functionality inside Django. > Moreover, it works with whatever DB I > happen to have configured my app to use at the time. You can use db agnostic pools like SQL Relay. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
