Changes between Version 10 and Version 11 of DjangoBranches


Ignore:
Timestamp:
Apr 29, 2008, 11:51:41 PM (17 years ago)
Author:
anonymous
Comment:

remove obsolete qs-rf info

Legend:

Unmodified
Added
Removed
Modified

  • DjangoBranches

    v10 v11  
    1010
    1111=== Database layer ===
    12  * [wiki:QuerysetRefactorBranch queryset-refactor]: A refactoring of the way queries are constructed in Django's database layer.
    13  * [wiki:ModelInheritance]: Write-up discussing how inheritance/subclassing of models should work. Currently this is not implemented in the development version of Django, so if you need model subclassing stick to one of the older stable releases or use workarounds like one-to-one relationships.
    1412 * [wiki:SchemaEvolution]: This is a new feature, under development as a project for the 2006 Summer of Code.
    1513 * [wiki:RowLevelPermissions]: Currently Django's permission system only works at the level of an entire model -- e.g., user "Bob" has access to add flatpages and edit users. This Summer of Code project will extend the permission system to be much more fine-grained, so permissions will be able to be assigned per object instead of per model (so, for example, user "Bob" could be given permission to edit only flatpage number 24 and user number 12, instead of all flatpages and all users).
    … …  
    3937
    4038Please note that the information regarding branches in the [http://www.djangoproject.com/documentation/contributing/#branch-policy Contributing] document is out of date with regards to Django's branch creation policy.
    41 
Back to Top