Using only('pk') in related set raises FieldDoesNotExist
|Reported by:||anonymous||Owned by:||GDorn|
|Component:||Database layer (models, ORM)||Version:||1.2|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||yes||Patch needs improvement:||yes|
This is my first ticket, apologies if this is known or I've missed something in my report.
With model A and model B, where model B has a fk to A:
Raises "FieldDoesNotExist: B has no field named 'pk'"
In my example I'm instantiating a new object for brevity. The behaviour is the same with a saved object.
I've attached a simple patch, however I couldn't get the testrunner working, so I couldn't write a full patch. Also, I expect this isn't the best method, but I don't know enough about the ORM to know of a better fix.
Change History (8)
Changed 3 years ago by sym.roe@…
comment:1 Changed 3 years ago by symroe
- Needs documentation unset
- Needs tests unset
- Patch needs improvement unset
comment:4 Changed 3 years ago by GDorn
- Owner changed from nobody to GDorn
- Status changed from new to assigned