Skip to content
Browse files

Fixed #17269 -- Corrected the model options doc to indicate that, sin…

…ce 1.4, all fields in `Meta.ordering` are honored by the admin. Thanks to sebastian for the report and patch.

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent 78a2719 commit aa5230c4be0a03153206397b191a1e79cae9ecd3 @jphalip jphalip committed
Showing with 4 additions and 5 deletions.
  1. +4 −5 docs/ref/models/options.txt
9 docs/ref/models/options.txt
@@ -189,11 +189,6 @@ Django quotes column and table names behind the scenes.
"-" prefix, which indicates descending order. Fields without a leading "-" will
be ordered ascending. Use the string "?" to order randomly.
- .. note::
- Regardless of how many fields are in :attr:`~Options.ordering`, the admin
- site uses only the first field.
For example, to order by a ``pub_date`` field ascending, use this::
ordering = ['pub_date']
@@ -206,6 +201,10 @@ Django quotes column and table names behind the scenes.
ordering = ['-pub_date', 'author']
+ .. versionchanged:: 1.4
+ The Django admin honors all elements in the list/tuple; before 1.4, only
+ the first one was respected.

0 comments on commit aa5230c

Please sign in to comment.
Something went wrong with that request. Please try again.