On Thu, 27 Jul 2006 18:41, James Bennett wrote: > On 7/27/06, John Morton <[EMAIL PROTECTED]> wrote: > > I have an app built who's data (shared lookup tables) is stored in it's > > own database. I want to pull those models into another application to map > > various codes in the second application's data to sensible user output, > > but I can't see a straight forward way of advising a particular imported > > model to use a specific set of database settings other than whatever the > > current setting context is. > > In the main Django trunk, there is no way to use more than one > database. However, the multi-db branch (which is still under > development and may contain bugs) is designed to allow any number of > databases to be used.
Ah - found some documentation for it here: http://code.djangoproject.com/wiki/MultipleDatabaseSupport I'll give it a spin. Thanks, John --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
