Code

Changes between Version 7 and Version 8 of DjangoBranches


Ignore:
Timestamp:
02/06/08 09:11:27 (6 years ago)
Author:
jbronn
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DjangoBranches

    v7 v8  
    1414 * [wiki:SchemaEvolution]: This is a new feature, under development as a project for the 2006 Summer of Code. 
    1515 * [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). 
    16  * [wiki:GeoDjango]: A branch for building GIS-enabled web applications.  Includes geometry-related fields and an interface for using Django's ORM with a spatial database (currently only PostGIS). 
     16 * [wiki:GeoDjango]: A branch for building GIS-enabled web applications.  Includes geometry-related fields and an interface for using Django's ORM with a spatial database (currently supports PostgreSQL/PostGIS, Oracle, and MySQL). 
    1717 * Generic relations: a "generic foreign key" feature is currently under development, but not yet completed. There is no support for it yet in the admin application, and it is probably unwise to attempt to use it in a production application. 
    1818