On Thu, Mar 12, 2009 at 11:42 PM, Adrian Holovaty <adr...@holovaty.com>wrote:
> > On Thu, Mar 12, 2009 at 7:59 PM, Alex Gaynor <alex.gay...@gmail.com> > wrote: > >> 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 :) ). > > Thanks, Alex. I've committed it in > http://code.djangoproject.com/changeset/10045 . > > Adrian > > > > Great, since we've moved so quickly on improving our plumbing for this there was one other idea I wanted to put forth(since I believe it needs to happen for any multidb implementation). In terms of plumbing the cornerstone of my multidb proposal is the addition of a django.db.connections object which lazily returns connections by subscripting based on a DATABASES option which is a dictionary of dictionaries. I think we could add support for this relatively easily, with full backwards compatibility. However, we only have 1 week until feature freeze so I wouldn't want to proceed with this unless everyone was completely comfortable with that proposed API, but I figured I'd bring it up since we have moved so quickly on these past bits. Any thoughts are welcome, 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 -~----------~----~----~----~------~----~------~--~---
