Changes between Version 13 and Version 14 of QuerysetRefactorBranch


Ignore:
Timestamp:
Apr 18, 2008, 9:31:08 PM (17 years ago)
Author:
anonymous
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • QuerysetRefactorBranch

    v13 v14  
    2525Along with, and as part of, all the bug fixes mentioned above there are a number of new features in the branch. A number of these features are purely internal details, but there are a few that add extra public functionality.
    2626
    27  1. Ordering querysets across related models has a new syntax that is the same as the way you specify relations in a filter: {{{field1__field2__field3}}}, etc. The new syntax is more natural and consistent, as well as helping solve a few bugs. See the {{{order_by()}}} documentation in db-api.txt for more information and some examples.
     27 1. Ordering querysets across related models has a new syntax that is the same as the way you specify relations in a filter: {{{field1__field2__field3}}}, etc. The new syntax is more natural and consistent, as well as helping solve a few bugs. See the {{{order_by()}}} documentation in [source:/django/branches/queryset-refactor/docs/db-api.txt db-api.txt] for more information and some examples.
    2828 2. Model inheritance is now possible. Both abstract base classes and multi-table inheritance are possible. See the [source:/django/branches/queryset-refactor/docs/model-api.txt model-api.txt] documentation for details.
    2929 3. The {{{__iter__()}}} method on querysets does not pull all the results into memory immediately. This reduces memory usage for large querysets where you don't end up accessing all the results. Queryset caching still occurs, though, so a single queryset object will only hit the database once. This change means that testing the boolean value of a queryset will only pull in the first few rows of the result, not all of them.
Back to Top