On Sat, 2006-06-17 at 07:27 +0000, william wrote:
>
[...]
> Sounds nice, this is a feature I'm currently looking for... but I've
> already started my own implementation.
>
> 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.
A drawback of this is that you pay the price when searching for "all
changes to field X since date D" or "show me a change history for field
X". You have to read and unpickle every single row before you can know
whether to discard it or not.
Another thing that occurs to me -- may not be relevant in your
particular situation, but does have general application -- unless you
are setting your timestamps manually (and it has sufficiently fine
granularity), you don't get a concept of a "changeset" of changes that
happen all at once, which does fall out of Uros's implementation.
> - type: type of modification (update, delete, insert).
> - "obj": the table object. This can come from ContentType
> - "obj_id": the id of the impacted object.
> - create_date: a timestamp automatically set.
Regards,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
