2009/7/3 Alex Gaynor <alex.gay...@gmail.com>: > > > On Fri, Jul 3, 2009 at 12:25 PM, Emily Rodgers > <emily.kate.rodg...@googlemail.com> wrote: >> >> >> >> On Jul 3, 3:29 pm, Emily Rodgers <emily.kate.rodg...@googlemail.com> >> wrote: >> > On Jul 1, 3:44 pm, Alex Gaynor <alex.gay...@gmail.com> wrote: >> > >> > >> > >> > > On Wed, Jul 1, 2009 at 9:39 AM, Emily Rodgers < >> > >> > > emily.kate.rodg...@googlemail.com> wrote: >> > >> > > > On Jul 1, 3:22 pm, Alex Gaynor <alex.gay...@gmail.com> wrote: >> > > > > On Wed, Jul 1, 2009 at 9:16 AM, Emily Rodgers < >> > >> > > > > emily.kate.rodg...@googlemail.com> wrote: >> > >> > > > > > On Jun 25, 6:45 pm, Alex Gaynor <alex.gay...@gmail.com> wrote: >> > > > > > > On Thu, Jun 25, 2009 at 10:24 AM, Tim Chase >> > > > > > > <django.us...@tim.thechases.com>wrote: >> > > > > > > > > Right now, Django doesn't seem to support the multiple >> > > > > > > > > databases on the same server or different servers. Will >> > > > > > > > > that >> > > > > > > > > feature be available out of the box for future releases? >> > >> > > > > > > > You may want to eavesdrop on the Django Developers group (as >> > > > > > > > opposed to this Django Users group) where Alex Gaynor has >> > > > > > > > been >> > > > > > > > posting updates on his GSoC project to add multi-DB support >> > > > > > > > to >> > > > > > > > Django[1]. There are several aspects to multi-DB support[2] >> > > > > > > > but >> > > > > > > > I believe he's addressing some of the more common use-cases. >> > > > > > > > You >> > > > > > > > can even follow along if you like to live dangerously as I >> > > > > > > > believe he's got a public repository for his code on GitHub. >> > >> > > > > > > > -tim >> > >> > > > > > > > [1] >> > >> > > >> > > > >http://groups.google.com/group/django-developers/search?group=django-. >> > > > > > .. >> > >> > > > > > > > [2] >> > >> > > >> > > > >http://groups.google.com/group/django-users/browse_thread/thread/6630. >> > > > > > .. >> > > > > > > > for my posted concerns >> > >> > > > > > > I have both a public code repository on github at >> > > > > > github.com/alex/django/ as >> > > > > > > well as a branch in Django's SVN at branches/soc2009/multidb. >> > > > > > > The >> > > > best >> > > > > > > place to find out about the work is the django-developers >> > > > > > > list, where >> > > > I >> > > > > > have >> > > > > > > sent any number of emails discussing both the overall design, >> > > > > > > as well >> > > > as >> > > > > > the >> > > > > > > status. >> > >> > > > > > > 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 >> > >> > > > > > Hi, >> > >> > > > > > Alex - do you know roughly when this is likely to be >> > > > > > incorporated into >> > > > > > django? I am working on a project that is going to need to >> > > > > > connect to >> > > > > > multiple databases (I am just planning / designing at the >> > > > > > moment), and >> > > > > > I want to know whether I should start investigating how to do >> > > > > > this >> > > > > > using django 1.0.2 or if that would be a waste of my time. >> > >> > > > > > If it is going to be a while, where would you suggest I start >> > > > > > looking >> > > > > > if I need to understand how to do it with django 1.0.2? >> > >> > > > > > Cheers, >> > > > > > Em >> > >> > > > > It will, at a minimum not occur until the end of the summer. >> > > > > Beyond that >> > > > I >> > > > > can't make any really useful guesses, other than to say that the >> > > > aggregation >> > > > > GSOC project from last summer >> > > > > ultimately made it's way into django trunk in January, about 3-4 >> > > > > months >> > > > > after the official end of GSOC. That may or may not ultimately be >> > > > > representative of how long it will take multi-db to make it's way >> > > > > back >> > > > into >> > > > > Django. A lot of it probably depends on how the 1.2/1.3 releases >> > > > > are >> > > > > scheduled. For example is 1.2 ends up being a smaller release >> > > > > that's put >> > > > > out in Novemberish I wouldn't expect multi-db to be considered for >> > > > > trunk >> > > > > until 1.3. Like I said all of that's rather speculative :) >> > >> > > > > 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 >> > >> > > > Thanks Alex. I don't think I can wait that long so it looks like I >> > > > am >> > > > going to have to get my hands dirty! >> > >> > > > Is this [1] a sensible starting point? >> > >> > > > [1] >> > > >> > > > >http://www.mechanicalgirl.com/view/multiple-database-connection-a-sim... >> > >> > > That blog post is a good source of information, as >> > > is:http://www.eflorenzano.com/blog/post/easy-multi-database-support-djan... >> > > unfortunately appears to be down right now). >> > >> > Hi, >> > >> > I have tried implementing this, but I am running into the problems >> > that others have about too many idle MySQL connections. Is there an >> > easy way to get around this? >> >> OK now I am running into even more problems :( >> >> I am probably being dumb, but I assumed there were only problems with >> foreign keys accross the different databases, but I am finding that I >> can't follow foreign keys from the secondary database to another table >> in the secondary database (even though both tables have the >> MultiDbManager defined for them). It just assumes all foreign keys are >> for tables in my primary database :( >> >> I may have to set up another script on another django project with a >> cli to get the data I want since I am only reading from the second db >> (it just seems to wrong!!). Or maybe just use mysqldb? >> > > Does your multidb manager have use_for_related_fields = True on it?
Ah - no. Thanks for spotting that! <trying it out> Yay - it worked. Thanks Alex :-) Still stuck on the too many connections thing. Will have to look into it on Monday though. Any ideas welcome. Em --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
