#20564: Querying (exclude) on a GenericRelation's DateTimeField through a
related
object fails
-------------------------------------+-------------------------------------
Reporter: nferrari | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version:
(models, ORM) | 1.6-alpha-1
Severity: Release blocker | Resolution: fixed
Keywords: contenttype exclude | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Anssi Kääriäinen <akaariai@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"31fd64ad8a98d7de0acb9144ae6f7bd124700cb0"]:
{{{
#!CommitTicketReference repository=""
revision="31fd64ad8a98d7de0acb9144ae6f7bd124700cb0"
Fixed #20564 -- Generic relations exclude() regression
The patch for #19385 caused a regression in certain generic relations
.exclude() filters if a subquery was needed. The fix contains a
refactoring to how Query.split_exclude() and Query.trim_start()
interact.
Thanks to Trac alias nferrari for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/20564#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 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.1ea5ba0c83d71c1aaea6e8ee6372f353%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
