i just implemented something like this. it useses decorator-syntax to create a denormalized field from a callable. i think the advantages of this aproach are: 1) it's very flexible 2) all code related to the denormalisiation is located in one central place, and not one place for the field definition and another place for the actual code
i also implemented a management command for rebuilding all the denormalisations. a (working) example: http://github.com/initcrash/django-denorm/tree/master/example/gallery/models.py the actual implementation of the decorator contains quite a few ugly hacks, maybe this can be done in a cleaner way by changing some code inside django itself. http://github.com/initcrash/django-denorm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
