#28101: Regression in nested __in subquery lookups when using to_field.
-------------------------------------+-------------------------------------
Reporter: Kristian Klette | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | 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 Simon Charette <charette.s@…>):
In [changeset:"0ad16934940fdbf0984f5255c7e5fff085593737" 0ad16934]:
{{{
#!CommitTicketReference repository=""
revision="0ad16934940fdbf0984f5255c7e5fff085593737"
[1.11.x] Fixed #28101 -- Fixed a regression with nested __in subquery
lookups and to_field.
Thanks Kristian Klette for the report and Tim for the help.
Backport of 8ef35468b660e1c25af67a8299202b8bc108679f from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28101#comment:9>
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/064.7ee146be2fa012e33d9952313f3ddea8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
