test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

[3.1.x] Refs #31502 -- Made minor edits to Model._state docs. 

Backport of 5ef6f62634 from master
This commit is contained in:
Adam Johnson 2020-07-15 10:27:46 +01:00 committed by Mariusz Felisiak
parent 54dce8148a
commit e63644d37b
2 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/ref/signals.txt
View File

@ -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 <django.db.models.Model._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::

7
docs/topics/db/multi-db.txt
View File

@ -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 <django.db.models.Model._state>` of the hint
instance. If a hint instance wasn't provided, or :attr:`instance._state.db
<django.db.models.Model._state>` is ``None``, the master router will allocate
the ``default`` database.
An example
----------