Changes between Version 27 and Version 28 of ModelInheritance
- Timestamp:
- Mar 31, 2006, 2:44:47 PM (19 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ModelInheritance
v27 v28 282 282 283 283 That should pretty much be it for the object side of things; what's left is the database side of things (ie, the hard part). 284 285 286 == Mixins == 287 here are two scenairos where mixins would be useful (to me). 288 289 1. 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. 290 291 2. 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