On Sat, Nov 5, 2011 at 1:33 PM, Furbee <furbeena...@gmail.com> wrote:
> No, that is incorrect. The Foreign key does not cross database boundaries.
> The employee table is in the secondary database, and the department table
> is also in the secondary database. The foreign key from from the employee
> table to the department table, both in the same secondary database.
>
>
OK, I found the ticket description very hard to follow so apparently
misunderstood. You don't mention having code any database routers for your
setup, that may be what you are missing. I don't believe you can do what
you are trying to do with just saying using('alternate_db') on retrieval of
an instance. I think you will need to code some database routing (
https://docs.djangoproject.com/en/1.3/topics/db/multi-db/#database-routers)
for this.
Karen
--
http://tracey.org/kmt/
--
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.
