Changes between Version 18 and Version 19 of QuerysetRefactorBranch


Ignore:
Timestamp:
04/27/08 01:33:36 (7 years ago)
Author:
simon
Comment:

Changed links to point at djangoproject.com/documentation equivalents

Legend:

Unmodified
Added
Removed
Modified
  • QuerysetRefactorBranch

    v18 v19  
    1111Along 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.
    1212
    13  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.
    14  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.
     13 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 [http://www.djangoproject.com/documentation/db-api/#order-by-fields  order_by() documentation] for more information and some examples.
     14 2. Model inheritance is now possible. Both abstract base classes and multi-table inheritance are possible. See the [http://www.djangoproject.com/documentation/model-api/#model-inheritance model-api documentation] for details.
    1515 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.
    1616 4. Slicing a queryset from a particular value to the end of a queryset is possible.
Back to Top