> Sounds nice, this is a feature I'm currently looking for... but I've
> already started my own implementation.
Nice! Do you have anyting in code yet? Any bottlenecks?
> I would just share it with you.
>
> I've build a single table History with :
> - "change"; a text field which will contain a python pickled
> dictionary: { field: old_value} in case you update a record.
How does this help/work? Why dictionary? Can you explain?
> - type: type of modification (update, delete, insert).
Is this really necesary? How do you make use of it?
> - "obj": the table object. This can come from ContentType
I don't understand...
> - "obj_id": the id of the impacted object.
> - create_date: a timestamp automatically set.
> I'm using it by sub-classing the save methods in each model I want to
> see the history.
> This is quite flexible, because you can decide which field you want to
> track.
I agree. But I fail to see the need for not versioning the whole record/row.
> To facilitate, yet one step further, it would be nice to have a
> PickledField within Model.models of django.
Can you elaborate on that?
> Feedbacks are welcome.
Same here! :) And thanks for your feedback!
Regards,
Uros
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
