Code

Opened 4 years ago

Closed 4 years ago

Last modified 3 years ago

#13216 closed (fixed)

Document the limitations on foreign keys and m2m relations across databases

Reported by: russellm 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: UI/UX:

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).

Attachments (0)

Change History (4)

comment:1 Changed 4 years ago by russellm

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted

comment:2 Changed 4 years ago by russellm

  • Resolution set to fixed
  • Status changed from new to closed

(In [13178]) Fixed #13216 -- Added clarifying note about cross-database relations.

comment:3 Changed 3 years ago by galund

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!)

comment:4 Changed 3 years ago by jacob

  • milestone 1.2 deleted

Milestone 1.2 deleted

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.