On Thu, Mar 12, 2009 at 1:26 PM, Yuri Baburov <burc...@gmail.com> wrote:
> > On Thu, Mar 12, 2009 at 11:44 AM, James Bennett <ubernost...@gmail.com> > wrote: > > > > On Wed, Mar 11, 2009 at 11:39 PM, Yuri Baburov <burc...@gmail.com> > wrote: > >> Maybe let's go a bit further towards pool of db connections and wrap a > >> bunch of lines importing backend into some function that depends on > >> engine argument? > > > > FWIW I'm still strongly of the opinion that database connection > > pooling does not belong in an ORM like Django's. > Dear James, > But I didn't tell whether connection pooling should belong to Django > ORM or not! And neither I told how do I understand "connection > pooling"... > > Let's just wrap those lines into a function! :) > > Adrian suggested a new way to write function get_db_wrapper in comments at > http://www.eflorenzano.com/blog/post/easy-multi-database-support-django/ > > But why not have a method get_db_engine(engine_name) in the Django ORM > code? > > -- > Best regards, Yuri V. Baburov, ICQ# 99934676, Skype: yuri.baburov, > MSN: bu...@live.com > > > > Yuri, FWIW that's on my list of stuff that would happen for multi-db support, but if someone wants to file a ticket and write up a patch(or I can) now that's certainly fine as it's really just code cleanup. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." --Voltaire "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
