On 6/19/06, IanSparks <[EMAIL PROTECTED]> wrote: > Although you have a date field in your example model it might not hurt > to add an automatic timestamp to a model that uses versioning in this > way.
Changing the versioned model because of use of versioning is something I would like to avoid. Forcing such things might not be a good idea. But if there is no other way... > One that relies on a "data" field that could be changed by a user > doesn't seem safe to me. I don't know what you mean by this? > 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? > You might also consider some automatic "revision number" system which > increments every time the record is changed. This makes it easier to > "roll back" to the previous entry and can be a lifesaver if something > happens to whatever is providing the dates. Every record in *_history table has its own ID which I was going to use as "revision number". And to make it easier to find "previous revision" I was thinking on adding a "prev_rev" column to the table. What do you think? Would this be enough? > I think the framework suggested is a great start. I would be interested > in seeing a feature that tied changes not just to the user who made the > change but also to the "session" that they made the change in. i.e. if > my system allows "Dave" to have two active sessions at different > computers I'd like to track what he did in each session not just what > date the changes occurred. This is very helpful for user complaints and > fraud detection. Hmm, very interesting idea! Do you have any suggestions on how would this be best implemented? I must admit, I don't have much knowledge how Django works internally so any help that I can get would be very appreciated! Thanks! Regards, Uros --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
