I'm trying to get rid of a weak Updates table that a coworker had been hacking up for use as a "user was changed on such and such day/ time..." and replace it with AuditTrail but there are a number of confounding issues.
AuditTrail: I don't have the User model overridden, how would I hook it into the user model? There doesn't appear to be a way to add request.user to the extra tracking fields as the callback function only gets passed the original instance pre-save. Hard to tell if any real recent changes have been made to it, making Django 1.2 compat a question mark. Django-Reversion: Seems to require a transactional database, however to my eternal chagrin, my coworkers have persistently used MySQL MyISAM. This appears to be a blocking issue preventing me from using reversion. By all means, correct me if I'm wrong. There also isn't any explicit mention of Django 1.2 compatibility. Django-audit-log appears to be abandoned. Is anyone aware of any functional alternatives or solutions to the blockers for using the above? Thank you for reading, :) --- Chris -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
