ordering by primary key in admin with oneToOne relations is done over the wrong table
|Reported by:||anonymous||Owned by:||Adrian Holovaty|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
If I use the admin application to browse for a relation that shares the primary key with another via an OneToOne fields, I take an error.
In my example, Person shares the primary key with Party, and browsing Person I take:
OperationalError at /admin/parties/persons/
(1109, "Unknown table 'parties_parties' in order clause")
It seems that the Sql related is
parties_persons ORDER BY
and I can see that the order by is done on the "father" table.
Of course, if I force a different order field with ordering = -dob?, for example, it's all o.k.