mirror of https://github.com/django/django.git
Fixed typo in docs/ref/models/options.txt
This commit is contained in:
parent
7211741fc5
commit
a89c856a7a
|
@ -192,7 +192,7 @@ Django quotes column and table names behind the scenes.
|
||||||
.. admonition:: Changing order_with_respect_to
|
.. admonition:: Changing order_with_respect_to
|
||||||
|
|
||||||
``order_with_respect_to`` adds an additional field/database column
|
``order_with_respect_to`` adds an additional field/database column
|
||||||
named ``_order``, so be sure to make and apply the appropriate
|
named ``_order``, so be sure to make and apply the appropriate
|
||||||
migrations if you add or change ``order_with_respect_to``
|
migrations if you add or change ``order_with_respect_to``
|
||||||
after your initial :djadmin:`migrate`.
|
after your initial :djadmin:`migrate`.
|
||||||
|
|
||||||
|
@ -266,7 +266,7 @@ Django quotes column and table names behind the scenes.
|
||||||
Determines if Django will use the pre-1.6
|
Determines if Django will use the pre-1.6
|
||||||
:meth:`django.db.models.Model.save()` algorithm. The old algorithm
|
:meth:`django.db.models.Model.save()` algorithm. The old algorithm
|
||||||
uses ``SELECT`` to determine if there is an existing row to be updated.
|
uses ``SELECT`` to determine if there is an existing row to be updated.
|
||||||
The new algorith tries an ``UPDATE`` directly. In some rare cases the
|
The new algorithm tries an ``UPDATE`` directly. In some rare cases the
|
||||||
``UPDATE`` of an existing row isn't visible to Django. An example is the
|
``UPDATE`` of an existing row isn't visible to Django. An example is the
|
||||||
PostgreSQL ``ON UPDATE`` trigger which returns ``NULL``. In such cases the
|
PostgreSQL ``ON UPDATE`` trigger which returns ``NULL``. In such cases the
|
||||||
new algorithm will end up doing an ``INSERT`` even when a row exists in
|
new algorithm will end up doing an ``INSERT`` even when a row exists in
|
||||||
|
|
Loading…
Reference in New Issue