id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
24479	Add a system check to prevent defining both ordering and order_with_respect_to	Daniel Hahler	Tim Graham <timograham@…>	"(In django/db/models/options.py)

1. When `order_with_respect_to` is being used, and value in `ordering` gets silently overwritten:

    self.ordering = ('_order',)

This should be documented.

2. Additionally, I am wondering if there should be a warning / hint when this happens, i.e. when `self.ordering` is non-empty.  It might be possible to keep any existing values, and prepend/append the `_order` value?!

3. With that code (`models.Options._prepare`), `ordering` gets set to `('_order',)` always (see point 1), but the proxy ""field"" gets only added if there's no `OrderWrt` field yet.  This could lead to having an invalid setting for `ordering`, in case there's a `OrderWrt` field that's not named `_order`?!

I think point 1 should be addressed anyway (apart from what gets done considering 2. and 3.)."	New feature	closed	Core (System checks)	dev	Normal	fixed		jon.dufresne@… me@…	Accepted	1	0	0	0	0	0