perrito666 wrote: > Ah thank you, ill keep an eye, so far the only think I did to it was a > small hack to handle the error raised by trying to copy a fk to the > audit table but it is a not very clean hack. > Perrito.
Took me an extra couple of days, but I've got all my modifications to AuditTrail posted here: http://code.djangoproject.com/wiki/AuditTrail Important bits: 1) ForeignKey and OneToOneFields supported (won't say fully tested for all cases, but they work in the simple ones) 2) Deletes are now tracked with saves (you can turn this behavior off if you want) 3) Type of change is tracked (currently can only distinguish between (insert/update) as a pair and delete) 4) Extra tracking fields on the audit models (and global fields that can be attached to all auditable models from one place) that can be tied into threadlocals (for tracking current user) 5) Different managers for instances and the class, so there are multiple options on how to filter (by only history of the current instance, or by the history of all things changed) I'm sure there's other things, but take a look and try it out. I'd be happy to get some feedback on this, what does and doesn't work for people, and especially some edge case testing like serialization. gav --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
