#13216 closed (fixed)
Document the limitations on foreign keys and m2m relations across databases
| Reported by: | Russell Keith-Magee | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 1.1 |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Many of the people investigating the new multi-db functionality are coming back to django-users and django-dev asking why they can't have a foreign key to an object on a remote database. We need to specifically document that this isn't possible (and why it isn't possible).
Change History (4)
comment:1 by , 15 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:3 by , 14 years ago
Don't necessarily want to reopen this ticket, but the documentation seems wrong. It appears to state that cross-database joins on MySQL with InnoDB are not possible, whereas in fact they are.
(So it is not surprising that many users might request this feature? - we'd certainly like it!)
Note:
See TracTickets
for help on using tickets.
(In [13178]) Fixed #13216 -- Added clarifying note about cross-database relations.