Code

Changes between Version 1 and Version 2 of DynamicModels


Ignore:
Timestamp:
05/09/07 12:47:12 (7 years ago)
Author:
Marty Alchin <gulopine@…>
Comment:

Fixed extra brackets around some links

Legend:

Unmodified
Added
Removed
Modified
  • DynamicModels

    v1 v2  
    9191 * {{{name}}} - The name of the model to be created 
    9292 * {{{fields}}} - A dictionary of fields the model will have (managers and methods would go in this dictionary as well) 
    93  * {{{app_label}}} - A custom application label for the model (this does not have to exist in your project, but see the [[#Admininterface Admin drawback]] below) 
     93 * {{{app_label}}} - A custom application label for the model (this does not have to exist in your project, but see the [#Admininterface Admin drawback] below) 
    9494 * {{{module}}} - An arbitrary module name to use as the model's source (prior to [5163], this had to be a real module path that had in fact been loaded) 
    9595 * {{{options}}} - A dictionary of options, as if they were provided to the inner {{{Meta}}} class 
    96  * {{{admin}}} - A dictionary of admin options, as if they were provided to the inner {{{Admin}}} class (again, see [[#Admininterface Admin drawback]] below) 
     96 * {{{admin}}} - A dictionary of admin options, as if they were provided to the inner {{{Admin}}} class (again, see [#Admininterface Admin drawback] below) 
    9797 
    9898Models can be created using this class with any number of features, as shown by the examples below. 
     
    197197}}} 
    198198 
    199 This doesn't take {{{Meta}}} or {{{Admin}}} options into account, nor does it allow for the creation of any model methods, but it's a decent example of how it could be done. Now a model can be created based on a database-backed description, as simply as this (but see the [[#Syncdb syncdb]] section for more details): 
     199This doesn't take {{{Meta}}} or {{{Admin}}} options into account, nor does it allow for the creation of any model methods, but it's a decent example of how it could be done. Now a model can be created based on a database-backed description, as simply as this (but see the [#Syncdb syncdb] section for more details): 
    200200 
    201201{{{