[patch] docs should explain that admin ignores all but first "ordering" argument in model
|Reported by:||pb@…||Owned by:||jacob|
|Cc:||Triage Stage:||Design decision needed|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
The admin only uses the first item in a model's "ordering" sequence. Attached is a simple documentation patch that notes this. Patch is for M-R docs but I'm sure trunk is nearly identical.
(I actually think this should ultimately be changed so that the full ordering sequence is respected by the admin, but having dug into the admin code a bit I appreciate that it's a non-trivial change, so I'm starting with the docs. I also know that multi-column ordering poses some thorny admin interface questions.)