In case the database is on the same host and technology (mysql, sqlite...) you could create a wrapper view in the databse django uses, to query data on the other database. At least that's what I did until such multi-db branch becomes stable!

Cheers,
Marc.

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.

Any idea how to do this?

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

Reply via email to