On Wed, May 11, 2011 at 4:56 AM, Shawn Milochik <sh...@milochik.com> wrote:
> > 1. I have a post_save signal listener and I dump the info about each model > instance with a timestamp and the pk of the user to MongoDB each time. The > main reason is for auditing purposes, but you can also use this data to > recreate missing records. > > This thread comes up at the right time when i myself was a little flummoxed with maintaining the sanctity of data(in terms of its history) and keeping a good audit log(of *ALL* actions - i.e, both from admin and non-admin[views.py] screens). I tried to evaluate the existing logging/revision apps like django-revision, django-simple-history and django-audit-log; but each of these creates identical tables from the 'base' table (and adds the audit columns) for which we want to keep the audit log. I am not sure how good this design is, as i havent worked on any such system. Has anyone done any performance tests of such a system. @Shawn : can you elucidate on how your system with MongoDB performs? -V http://blizzardzblogs.blogspot.com/ -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
