I believe the idea is being thrown around on how to properly implement something like that as part of Django. However having access to the currently logged in user from the model creates a dependency to the auth middleware which is not very elegant.
So while the experts are throwing that idea around someone else suggested a piece of middleware that stores the current user in thread local storage. Which means you can get the current user in the an overloaded save method for your model. Here's the Wiki link http://code.djangoproject.com/wiki/CookBookThreadlocalsAndUser --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users -~----------~----~----~----~------~----~------~--~---
