#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: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | 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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"b81e974e9ea16bd693b194a728f77fb825ec8e54" b81e974]:
{{{
#!CommitTicketReference repository=""
revision="b81e974e9ea16bd693b194a728f77fb825ec8e54"
Fixed #34604 -- Corrected fallback SQL for n-ary logical XOR.
An n-ary logical XOR Q(…) ^ Q(…) ^ … ^ Q(…) should evaluate to true
when an odd number of its operands evaluate to true, not when exactly
one operand evaluates to true.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34604#comment:4>
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/010701889e6c3c3b-cf59e4b2-a9c0-4fb1-990d-a2ee4a54e338-000000%40eu-central-1.amazonses.com.
