Damn - no thoughts on this from anyone? On Wed, Jan 25, 2012 at 12:11 AM, Cal Leeming [Simplicity Media Ltd] < [email protected]> wrote:
> Hi all, > > After spending about 30 minutes looking through old tickets, long > discussion threads and various blogs, I'm still not clear on the MySQL > connection pooling topic. > > To quote Russ: "the capability already exists in third party tools, and > they're in a position to do a much better job at it than us because it's > their sole focus" [3] > > Could a core dev (or anyone else with experience on this) clarify which > approach is recommended, on the following conditions: > > * Safety (should not cause any strangeness with query cache or ORM) > * Performance (should avoid causing Django to open a new database > connection on every request) > > I found various ways to accomplish this, one of which was to use > SQLalchemy[1], another was to stop Django from closing the database > connection after each query[2]. > > I'm hoping this thread will also serve as a final answer for anyone else > looking for clarification. > > Many thanks > > Cal > > [1] > http://menendez.com/blog/mysql-connection-pooling-django-and-sqlalchemy/ > [2] > http://stackoverflow.com/questions/1125504/django-persistent-database-connection > [3] > http://groups.google.com/group/django-developers/browse_thread/thread/6f1e9c6e81aff1de/bf34e546e4217277?lnk=gst&q=mysql+pooling#bf34e546e4217277 > > > -- 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.
