Fixed #29762 -- Document how database routers are used for related-object access. #20292
+47
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Trac ticket number
ticket-29762
Branch description
This PR documents how Django selects the database for related-object access in multi-database configurations.
Django records the originating database on
instance._state.dband uses it for related lookups.When a database router overrides
db_for_read()without considering theinstancehint, this default behavior is lost, which can cause errors in multi-schema setups.The patch adds a section explaining the default behavior, the use of
hints, and how routers should preserve correct routing.Checklist
mainbranch.