Hi! > Great to see that your RFC is pretty much exactly what I was thinking > (feature and implementation-wise) when I posted > http://roups.google.com/group/django-developers/browse_thread/thread/d90001b1d043253e/77d36caaf8cfb071
I'm glad! Thanks for the link too. > 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. But it's something that it should be made possible with additional/custom fields, IMHO. > I thought that storing complete row copies on both inserts and updates > to original object isn't that bad - it certainly simplifies the > machinery. This is true. > 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. I'm sort-of undecided about this. On one hand you can potentialy have a lot more data to handle, but on the other, you don't need multiple SELECTs and merging happen when you want a version from way back. What do others think about this? > An admin to view change history "diff" colored output and to revert to > arbitrary previous version would be an obvious future addition. I agree. And I do have it on my todo list, but it's not "feature critical", so it will have to wait until the machinery is done. Or maybe not... hmm... 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 -~----------~----~----~----~------~----~------~--~---
