#29214: Invalid SQL generated when annotating a subquery with an outerref to an
annotated field.
-------------------------------------+-------------------------------------
Reporter: Oskar Persson | Owner: Chetan
| Khanna
Type: Bug | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: queryset | Triage Stage: Accepted
annotations |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Chetan Khanna):
* owner: nobody => Chetan Khanna
* status: new => assigned
* has_patch: 0 => 1
Comment:
Yes, it sure is tricky!
https://github.com/django/django/pull/12546
I have prepared a patch that should work for the update case at least. And
sorry for prolonging this, I had my university exams in the middle and the
implementation didn't come to me at once but I still wanted to give it a
shot. I've tried to follow whatever was said in
https://code.djangoproject.com/ticket/29214#comment:12 as closely as
possible. Awaiting review :)
--
Ticket URL: <https://code.djangoproject.com/ticket/29214#comment:15>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.1c116fe178361f2312dacb4184c40e82%40djangoproject.com.
