#26891: ForeignObject/ForeignKey does not obey lookup registration API
----------------------------------------------+--------------------
Reporter: rpkilby | Owner: nobody
Type: Bug | Status: new
Component: Database layer (models, ORM) | Version: 1.9
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 0 | UI/UX: 0
----------------------------------------------+--------------------
`ForeignObject`'s implementation of `get_lookup` and `get_transform`
causes `register_lookup` to essentially have no effect.
The PR should allow users to successfully register lookups while ignoring
the default lookups registered to the `Field`. This works by duplicating
`RegisterLookupMixin._get_lookup`, but stopping mro walking at
`ForeignObject`.
https://github.com/django/django/pull/6906
--
Ticket URL: <https://code.djangoproject.com/ticket/26891>
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/050.88b8852fc5326c9bd162d747f3351528%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
