#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:  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):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin
 * needs_docs:  1 => 0


-- 
Ticket URL: <https://code.djangoproject.com/ticket/34604#comment:3>
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/010701889a3edce0-230b834a-97b4-4a2f-9fd1-8b37deac25e7-000000%40eu-central-1.amazonses.com.

Reply via email to