As I started writing the test for this, I realized I would have to inspect
the query itself, which seems... like a bad idea for a test. Would this be
reasonable to submit the (one-line-change) patch without a test, or does
someone have a suggestion for a way to make the test that's less brittle?
--
Ticket URL: <https://code.djangoproject.com/ticket/24296>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* needs_docs: => 0
* needs_tests: => 0
* stage: Unreviewed => Accepted
Comment:
A test that inspects the query is likely fine. See if you can find an
existing test that does something similar.
--
Ticket URL: <https://code.djangoproject.com/ticket/24296#comment:1>
* owner: nobody => Marcelo Galigniana
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/24296#comment:2>
Comment (by Marcelo Galigniana):
[https://github.com/django/django/pull/15576 PR was created]
--
Ticket URL: <https://code.djangoproject.com/ticket/24296#comment:3>
* has_patch: 0 => 1
* stage: Accepted => Ready for checkin
--
Ticket URL: <https://code.djangoproject.com/ticket/24296#comment:4>
* 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>