Changes between Version 35 and Version 36 of ModelInheritance


Ignore:
Timestamp:
06/09/2006 02:39:25 AM (9 years ago)
Author:
wcsc.erode@…
Comment:

Adding info for automatic auditing functionality

Legend:

Unmodified
Added
Removed
Modified
  • ModelInheritance

    v35 v36  
    3103101. auditing. I would like to have certain models have a created by/time and last-updated by/time on the record, and possibly a XXX_history table which shows the previous version on that entry when it gets changed.
    311311
     312One way to implement this very useful and needed functionality may be to have a builtin 'log' model class containing modified_by/time (should be populated withour user input), reason for modification (user comments) ..etc. We can inherit this in our models when necessary and voila! our classes would have an additional myproj_myapp_log table for auditing purposes. This table would contain all the fields of the class before modification with the extra fields from the log class. This log table should additionally be non-editable. Only inserts should be possible. No deletes/modifications. Mysql has an 'archive' table type to facilitate this. Other DBs should have their corresponding types. This feature, I think will appeal to many. "Django - The framework with Inbuilt data auditing" - The IT Departments will love this.
     313
    3123142. tagging. I would like to 'mark' a model as being taggable, and let the mixin worry about the rest. This I could do now by overriding the many2many field type, but I think a mixing would be nicer
    313315
Back to Top