#25991: A new implementation for exclude() queries
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by akaariai):
Related tickets:
- https://code.djangoproject.com/ticket/14645
- https://code.djangoproject.com/ticket/18726
- https://code.djangoproject.com/ticket/21703
- https://code.djangoproject.com/ticket/23797
- https://code.djangoproject.com/ticket/24386
The first one (#14645) deals with the issue mentioned in this ticket's
description. It should be fixed by this ticket. The rest of the tickets
are various failures in .exclude() queries, and these might be fixed by
this ticket, but I haven't verified those yet.
--
Ticket URL: <https://code.djangoproject.com/ticket/25991#comment:1>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.79149358fd0c608958a242e2b06343b4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
