#26983: Boolean filter "field__isnull=False" not working with ForeignKey with
to_field
-------------------------------------+-------------------------------------
Reporter: weidwonder | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: queryset | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by lamby):
After writing a testcase (available here:
https://gist.github.com/lamby/394b712e9e9ff1e868a20e67d4ba482b/raw) "git
bisect" told me that it was indeed fixed with the above change.
Investigating more, what happened was that I was applying the patch
against `RelatedIn`instead of `RelatedLookupMixin`. Apologies for the
noise there.
''However'', I am still correct in that the bug is not strictly `to_field`
specific as it affects this `primary_key` case. Therefore, I suggest:
* You update the release documentation, etc. to reflect this
* You add my test (or similar) to prevent a regression
In light of this, I am not resolving this ticket so that these action
items do not get overlooked.
--
Ticket URL: <https://code.djangoproject.com/ticket/26983#comment:12>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.7ebaf9333921cca0520aed5988b70d1f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
