#22648: Overridden get_lookup/get_transform not chainable
-------------------------------------+-------------------------------------
Reporter: mjtamlyn | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) | Resolution: fixed
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by Marc Tamlyn <marc.tamlyn@…>):
In [changeset:"c38925a6018a7943936d1fd2b9038ab5de406545"]:
{{{
#!CommitTicketReference repository=""
revision="c38925a6018a7943936d1fd2b9038ab5de406545"
[1.7.x] Fixed #22648 -- Transform.output_type should respect overridden
custom_lookup and custom_transform.
Previously, class lookups from the output_type would be used, but any
changes to custom_lookup or custom_transform would be ignored.
Backport of a2dd618 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/22648#comment:4>
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/066.7ce6d44426f1a01bc19b59f174eaf86d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
