#34604: On databases lacking XOR, Q(…) ^ Q(…) ^ Q(…) wrongly interpreted as
exactly-one rather than parity
-------------------------------------+-------------------------------------
Reporter: Anders Kaseorg | Owner: Anders
| Kaseorg
Type: Bug | Status: assigned
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* cc: Ryan Heard (added)
* needs_better_patch: 0 => 1
* stage: Unreviewed => Accepted
* needs_docs: 0 => 1
Comment:
Thanks for the report.
[https://github.com/django/django/pull/16901 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/34604#comment:2>
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/010701886be85ef9-8a7d1b6d-9236-4b5f-b930-2325d3367477-000000%40eu-central-1.amazonses.com.
