> > 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 [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
