On Thu, Mar 12, 2009 at 7:04 PM, Adrian Holovaty <adr...@holovaty.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?
> > And later call it with settings.DATABASE_ENGINE to import default
> backend.
> >
> >
> http://code.djangoproject.com/browser/django/trunk/django/db/__init__.py?rev=10026
> > Lines 12-38.
>
> Yes, good idea, Yuri! It would be nice to encapsulate the logic of
> loading the appropriate Django database backend class from
> django.db.backends based on a given backend name.
>
> I've created a ticket here:
>
>    http://code.djangoproject.com/ticket/10487
>
> If anybody (Alex?) wants to code up a patch, I'll get it in ASAP.
>
> Adrian
>
> >
>
I've gone ahead and uploaded a patch(at this rate they'll be nothing to do
over the summer :) ).

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
-~----------~----~----~----~------~----~------~--~---

Reply via email to