#27862: Exists() feature generates invalid SQL query on postgres backend
-------------------------------------+-------------------------------------
Reporter: Vasily Stepanov | Owner: Matthew
| Schinckel
Type: Bug | Status: assigned
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: Queryset Subquery | Triage Stage: Accepted
Exists |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Matthew Schinckel):
* has_patch: 0 => 1
Comment:
So, I think I have a fix for this: it fixes this specific use case, but
I'm at a loss as to if it will break something else.
PR is at https://github.com/django/django/pull/8115
--
Ticket URL: <https://code.djangoproject.com/ticket/27862#comment:7>
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/072.f588e8e3e8d13ce170501e97d3dfb73a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
