Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#29349 closed Cleanup/optimization (fixed)

Document that database routing disallows cross-database relations by default

Reported by: Stefan R. Filipek Owned by: Stefan R. Filipek
Component: Documentation Version: dev
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

The documentation is not clear what happens when all routers return None from allow_relation.

The default behavior is to only allow relations within the same database. To allow cross-database relations, some router must return True.

Change History (5)

comment:1 by Stefan R. Filipek, 6 years ago

Owner: changed from nobody to Stefan R. Filipek
Status: new → assigned

comment:2 by Stefan R. Filipek, 6 years ago

Has patch: set

Pull request: ​https://github.com/django/django/pull/9893

comment:3 by Tim Graham, 6 years ago

Summary: Improve documentation regarding allow_relation → Document that database routing disallows cross-database relations by default
Triage Stage: Unreviewed → Accepted

comment:4 by Tim Graham <timograham@…>, 6 years ago

Resolution: → fixed
Status: assigned → closed

In 9ec77f3d:

Fixed #29349 -- Doc'd the default behavior of router.allow_relation().

comment:5 by Tim Graham <timograham@…>, 6 years ago

In 9f2586b:

[2.0.x] Fixed #29349 -- Doc'd the default behavior of router.allow_relation().

Backport of 9ec77f3d6633691c9bbf31d10af2313689170c85 from master

Note: See TracTickets for help on using tickets.
Back to Top