#32717: Incorrect SQL generation filtering OR-combined queries
-------------------------------------+-------------------------------------
Reporter: Shaheed Haque | Owner: Simon
| Charette
Type: Bug | Status: assigned
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Shaheed Haque):
Hi,
I'm not qualified to speak to most of this, but I'm wanted to check if "we
should prevent Query.combine from ever generating queries with root
Where(connector='OR')" means that the original OR'd query I wrote would
not be supported?
If so, then how else could one write the query? (As I said, I don't see
how Q() can be used with .exclude()...but I might have missed something).
--
Ticket URL: <https://code.djangoproject.com/ticket/32717#comment:5>
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.4d1cbb2d993e2840f4297de46f789802%40djangoproject.com.
