Documentation for slicing QuerySets is misleading
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)
| Component: |
Admin interface → Documentation
|
| Owner: |
changed from Adrian Holovaty to Jacob
|
| Version: |
→ magic-removal
|
| Resolution: |
→ fixed
|
| Status: |
new → closed
|
(In [2837]) Fixed #1733 -- Clarified docs/db-api.txt section on slicing QuerySets. Thanks, Luke Plant