Opened 19 years ago
Closed 19 years ago
#877 closed defect (duplicate)
ordering by primary key in admin with oneToOne relations is done over the wrong table
Reported by: | anonymous | Owned by: | Adrian Holovaty |
---|---|---|---|
Component: | contrib.admin | Version: | dev |
Severity: | normal | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
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
select
['parties_persons
.party_id
',..., 'parties_persons
.last_modified
']
sql
' FROM parties_persons
ORDER BY parties_parties
.id
DESC'
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.
This is the same as ticket:930 I think, which has a patch attached.