In documentation there is a small note about fields being supported in
PostgreSQL only. Almost all examples though uses fields provided which
works only in PostgreSQL. It gives impression if reader does just a quick
look of examples that passing parameters is common operation which works
everywhere.
Examples should use common format that works for everybody and with a note
add database spesifics.
--
Ticket URL: <https://code.djangoproject.com/ticket/20561>
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:
I think there is room for some improvement here. Maybe the whole thing
should be split to .distinct() and .distinct(*fields)?
--
Ticket URL: <https://code.djangoproject.com/ticket/20561#comment:1>
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"577b0f91894469872974ad609b4fabca949cdc1b"]:
{{{
#!CommitTicketReference repository=""
revision="577b0f91894469872974ad609b4fabca949cdc1b"
Fixed #20561 -- Emphasized that QuerySet.distinct([*fields]) is only
supported by Postgres.
Thanks jtiai for the suggestion.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/20561#comment:2>
Comment (by Tim Graham <timograham@…>):
In [changeset:"430aae1b0db9fbcc15415b7bd9a14df1d88359cf"]:
{{{
#!CommitTicketReference repository=""
revision="430aae1b0db9fbcc15415b7bd9a14df1d88359cf"
[1.6.x] Fixed #20561 -- Emphasized that QuerySet.distinct([*fields]) is
only supported by Postgres.
Thanks jtiai for the suggestion.
Backport of 577b0f9189 from master.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/20561#comment:3>