Also, https://github.com/niwibe/djorm-ext-pool is based initially on postgresspool but works with sqlite and mysql.
The only difference is that uses monky patching instead a separate backend. We also use it in production on a project a while ago and has not given us any problems. Andrey 2013/2/17 Carl Meyer <c...@oddbird.net> > On 02/17/2013 11:31 AM, Anssi Kääriäinen wrote: > > It seems SQLAlchemy has a mature pooling implementation. So, yet > > another approach is to see if SQLAlchemy's pooling implementation > > could be reused. (Maybe in conjunction with the above 'POOLER' idea). > > There is in fact an implementation of reusing SQLAlchemy's connection > pool with Django (via DatabaseWrapper subclassing): > https://github.com/kennethreitz/django-postgrespool/ > > I have this in production for several months with no issues, so the > concept certainly works. > > Carl > > -- Andrey Antukh - Андрей Антух - <n...@niwi.be> http://www.niwi.be/about.html http://www.kaleidos.net/A5694F/ "Linux is for people who hate Windows, BSD is for people who love UNIX" "Social Engineer -> Because there is no patch for human stupidity" -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
