Thanks for the link, it is very helpful. I see the last attachments are the docs committed by you -- I'll be giving those a read here shortly.
As an aside, I think it is a real showstopper to not include this feature in the main trunk... I can't believe the triage stage on the feature request was recently changed to "Someday/Maybe". To me it seems obvious that all of the data that a Django app could need might not reside on the same database for any number of reasons. Perhaps I'll put some work into this when I have some time and get it caught up with the latest trunk. Derek [EMAIL PROTECTED] wrote: > There is a Multiple Database Branch which is not under active > development...and doesn't have some of the new stuff in the > trunk...but I'm using it in one of my projects...works pretty good for > the most part. > > http://code.djangoproject.com/wiki/MultipleDatabaseSupport > > On Dec 11, 2:48 pm, Derek Steinkamp <[EMAIL PROTECTED]> wrote: > >> I read through all the relevant documentation but I couldn't find any >> info on an issue I am about to face: accessing multiple tables in >> different databases with Django. >> >> Here's a quick example: >> My Django app (MyApp) has r/w access to the MyApp database on >> MySQLserver1, and all of MyApp models live within here. I now need to >> access a pre-existing database/table on MySQLserver2 to bring in some >> data relevant to MyApp. >> >> My ultimate question is: does Django support accessing models that live >> in/on different databases/servers within one app? If so, how do I do >> this? If not, what should I be doing? >> >> Thanks, >> Derek >> > > > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
