Thank you for sharing. Yes, the model is not difficult, that's why everybody helps himself up to now. Maybe this is the best solution and there is not much in common.
The things which are in common (ORM, Admin-Interface) are already provided by django. It's just a bit of glue-code to get it working. Again, thank you for sharing your solution. Regards, Thomas Am Samstag, 8. April 2017 18:58:59 UTC+2 schrieb Scot Hacker: > > On Tuesday, April 4, 2017 at 5:18:42 AM UTC-7, guettli wrote: >> >> In the past I was told: Don't store logs in the database. >> > > For general purposes, I agree with this. Logging is a python standard, > logs can be verbose, logrolling solutions are well established (and built > in), etc. However, there are certain situations or activities where > database logging makes sense, most likely *in addition to* standard logging > rather than instead of. In one of my projects, half a dozen non-technical > managers need the ability to track certain types of actions (related to > account activations at a school). For this, I developed a simple ORM > logging solution that lets those managers search and filter these special > logs in the Django admin. > > It's not something that really deserves to be its own project, IMO - just > a typical thing a dev might do in Django to satisfy an institutional need. > But I've put my solution in this gist, in case its helpful: > > https://gist.github.com/shacker/05bc1de527a2d7412de361ac659aecde > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/e20e56bd-e82c-4027-afa2-bc08ca35c00b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
