Opened 17 years ago
Closed 16 years ago
#5812 closed (invalid)
Misleading sentence in the database api reference
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
On http://www.djangoproject.com/documentation/db-api/ I'm reading:
"The people who made Django prefer to put all the SQL-affecting methods first, followed (optionally) by any output-affecting methods (such as values()), but it doesn’t really matter."
This leads to the impression that values() does not affect the SQL statement of the query set which it purportedly does!
Note:
See TracTickets
for help on using tickets.
It's more of a general guideline, not something meant to indicate that
values()can't change the query.