Re: RFC: Django history tracking
Hi Uros, Great to see that your RFC is pretty much exactly what I was thinking (feature and implementation-wise) when I posted http://groups.google.com/group/django-developers/browse_thread/thread/d90001b1d043253e/77d36caaf8cfb071 It would be nice to record "who" made the change (optionally when there is a user with an id available). I thought that storing complete row copies on both inserts and updates to original object isn't that bad - it certainly simplifies the machinery. Because the way I was considering using this feature would read history tables very infrequent their size wasn't a big factor in my mind. An admin to view change history "diff" colored output and to revert to arbitrary previous version would be an obvious future addition. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: RFC: Django history tracking
> > It would be nice to record "who" made the change (optionally when there > > is a user with an id available). > > I was thinking of not pushing the use of such fields, because there is > no easy way to figure out how each applications handles > accounts/users. and > > I'd also like an automatic userid stamp on there over and above the > > "author" which again is a data field not a hidden system field. > > As I said before, this is not something that can be easily done, > because various ways of user/account handling. Or am I missing the > point here? I think using django.contrib.auth's user id (when available) would be satisfactory for most people. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Object (not schema) versioning/history
As I am thinking about using Django for a particular project I was wondering if anyone ever considered keeping track of object content history. For example, in a typical CMS/newspaper application with multiple contributors I'd like to keep track of actual changes made to some pieces of content by all users. Ultimately, I'd like to be able to go through current "Changed field x, y, z." history entries, click on them and see a diff-like output of actual changes made. These records would be very infrequently accessed (in my worldview, anyway), and perhaps generally infrequently created. I would love to be able to put @versioned on top of a model and then have it automatically create an app_model_history table and record things in it appropriately on save(). Does that excite anyone else? SoC project? ;) --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
