> Most ideally we would like to have it so that the application uses DB1 > (defined in the settings.py file) as the main database, but when it's > down to users, uses DB2.user as the users table. > Currently we are thinking of using raw sql, but that would only be a > last resort preferably. And at that point I'd be more scrambled on how > to use authenticate together with it. > > If you are using MySQL, you can use the federated engine for tables that are only "symlinks" to real tables in another database but will act as normal tables when doing regular operations on them.
It might be possible with other databases too, I don't know. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
