From 5ef6f626347f9ea13915f3cf5b8b045c5b42b102 Mon Sep 17 00:00:00 2001 From: Adam Johnson Date: Wed, 15 Jul 2020 10:27:46 +0100 Subject: [PATCH] Refs #31502 -- Made minor edits to Model._state docs. --- docs/ref/signals.txt | 8 ++++---- docs/topics/db/multi-db.txt | 7 ++++--- 2 files changed, 8 insertions(+), 7 deletions(-) diff --git a/docs/ref/signals.txt b/docs/ref/signals.txt index dc8c53ac2d..a4ed248769 100644 --- a/docs/ref/signals.txt +++ b/docs/ref/signals.txt @@ -101,10 +101,10 @@ Arguments sent with this signal: .. note:: - ``instance._state`` isn't set before sending the ``post_init`` signal, - so ``_state`` attributes always have their default values. For example, - ``_state.db`` is ``None`` and cannot be used to check an ``instance`` - database. + :attr:`instance._state ` isn't set + before sending the ``post_init`` signal, so ``_state`` attributes + always have their default values. For example, ``_state.db`` is + ``None``. .. warning:: diff --git a/docs/topics/db/multi-db.txt b/docs/topics/db/multi-db.txt index a01ce52f38..f4357642e6 100644 --- a/docs/topics/db/multi-db.txt +++ b/docs/topics/db/multi-db.txt @@ -239,9 +239,10 @@ database usage. Whenever a query needs to know which database to use, it calls the master router, providing a model and a hint (if available). Django then tries each router in turn until a database suggestion can be found. If no suggestion can be found, it tries the -current ``_state.db`` of the hint instance. If a hint instance wasn't -provided, or the instance doesn't currently have database state, the -master router will allocate the ``default`` database. +current :attr:`instance._state.db ` of the hint +instance. If a hint instance wasn't provided, or :attr:`instance._state.db +` is ``None``, the master router will allocate +the ``default`` database. An example ----------