#20168 closed Cleanup/optimization (fixed)
PostgreSQL specific example in documentation
Reported by: | Russell Keith-Magee | 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: | yes | UI/UX: | no |
Description
The documentation on Custom manager objects uses an example for a custom method that opens a database cursor. However, the example uses a PostgreSQL-specific SQL dialect in the GROUP BY clause (the use of column numbers in the GROUP BY clause).
This is potentially confusing; using a more conventional GROUP BY clause referencing column names would be no less confusing for PostgreSQL users, but would make sense to those coming from other databases.
Note:
See TracTickets
for help on using tickets.
In c119d0f152e939420613868294d58fa4b902e18a: