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.
Furbeenator On Sat, Nov 5, 2011 at 10:26 AM, Django <nore...@djangoproject.com> wrote: > #17167: ModelForm model=class not honoring reference fields with secondary > database > -------------------------------------+------------------------------------- > Reporter: furbeenator@… | Owner: nobody > Type: Bug | Status: closed > Component: Forms | Version: 1.3 > Severity: Normal | Resolution: invalid > Keywords: ModelForm, using(), | Triage Stage: > foreign key, reference field | Unreviewed > Has patch: 0 | Needs documentation: 0 > Needs tests: 0 | Patch needs improvement: 0 > Easy pickings: 0 | UI/UX: 0 > -------------------------------------+------------------------------------- > Changes (by kmtracey): > > * status: new => closed > * resolution: => invalid > > > Comment: > > Near as I can tell you are trying to have !ForeignKeys that cross database > boundaries. This is not supported by Django's multiple database support, > see: https://docs.djangoproject.com/en/1.3/topics/db/multi-db/#cross- > database-relations > > -- > Ticket URL: <https://code.djangoproject.com/ticket/17167#comment:2> > Django <https://code.djangoproject.com/> > The Web framework for perfectionists with deadlines. > -- 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.
