#10414: select_related ignores unrecognized fields
-------------------------------------+-------------------------------------
Reporter: trebor74hr | Owner: nip3o
Type: Bug | Status: assigned
Component: Database layer | Version:
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: select_related | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by nip3o):
* needs_better_patch: 1 => 0
Comment:
I have forgotten about this for quite a while, but the patch was updated
to support using non-relational fields quite a while ago (including tests
for this case, of course). I just updated the pull-request to the latest
version of master, so it should be ready to merge if all tests pass at the
CI server. Can I trig a CI build myself or can only core developers do
that?
--
Ticket URL: <https://code.djangoproject.com/ticket/10414#comment:25>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.42283b12e585547fca47b362049bdfc8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.