Opened 18 years ago

Closed 18 years ago

Last modified 18 years ago

#1733 closed defect (fixed)

Documentation for slicing QuerySets is misleading

Reported by: Luke Plant Owned by: Jacob
Component: Documentation Version: magic-removal
Severity: normal 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

The documentation on When QuerySets are evaluated is misleading in the 'slicing' section. The implementation of slicing changed in order to support everything that could be done with the old generic views, and now, slicing always creates a new QuerySet (i.e. doesn't affect the existing one at all). It will return a list of objects if the slice can't be done in SQL (such as if the 'step' parameter is used), or if a single object is requested -- otherwise it will return a new QuerySet.

Change History (2)

comment:1 by Luke Plant, 18 years ago

Component: Admin interfaceDocumentation
Owner: changed from Adrian Holovaty to Jacob
Version: magic-removal

comment:2 by Adrian Holovaty, 18 years ago

Resolution: fixed
Status: newclosed

(In [2837]) Fixed #1733 -- Clarified docs/db-api.txt section on slicing QuerySets. Thanks, Luke Plant

Note: See TracTickets for help on using tickets.
Back to Top