Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Fixed typo in docs/ref/models/options.txt

  • Loading branch information...
commit a89c856a7aadc830951342a1fa49c1a1b5ac9156 1 parent 7211741
@timgraham timgraham authored
Showing with 2 additions and 2 deletions.
  1. +2 −2 docs/ref/models/options.txt
View
4 docs/ref/models/options.txt
@@ -192,7 +192,7 @@ Django quotes column and table names behind the scenes.
.. admonition:: Changing order_with_respect_to
``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``
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
:meth:`django.db.models.Model.save()` algorithm. The old algorithm
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
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
Please sign in to comment.
Something went wrong with that request. Please try again.