#24296: clear select fields for `.exists()` of distinct, non-sliced querysets
-------------------------------------+-------------------------------------
Reporter: Martin Chase | Owner: Marcelo
Type: | Galigniana
Cleanup/optimization | Status: closed
Component: Database layer | Version: 1.7
(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:"0ad5316f22eabe8fa8b22dc92e61170cfacc3c78" 0ad5316f]:
{{{
#!CommitTicketReference repository=""
revision="0ad5316f22eabe8fa8b22dc92e61170cfacc3c78"
Fixed #24296 -- Made QuerySet.exists() clear selected columns for not
sliced distinct querysets.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24296#comment:5>
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/010701801d2624ca-04486988-01ae-47a2-ba1b-079cbeb655b7-000000%40eu-central-1.amazonses.com.
