#20561 closed Uncategorized (fixed)
QuerySet .distinct([*fields]) documentation improvements
| Reported by: | Jani Tiainen | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 1.5 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
QuerySet does have .distinct([*fields]) method has optional feature to provide fields that are used on distinct. This feature is supported only by PostgreSQL.
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.
Change History (3)
comment:1 by , 12 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I think there is room for some improvement here. Maybe the whole thing should be split to .distinct() and .distinct(*fields)?