On Jan 17, 2008 5:00 AM, Grindizer <[EMAIL PROTECTED]> wrote: > - If you want to retrieve the current logged user at model level, this > is a little more complicated, because models are note designed to see > what happen at process level, but it still possible, look at this:
Any code which requires this is, in my opinion, badly designed and should be re-thought so that it accesses the user object from a context where it's already naturally available -- preferably in a view which has access to the HttpRequest object. It's easy enough to pass the request, or the logged-in user read from the request, to functions on an as-needed basis, and doing so is much clearer and much less hackish than the threadlocals trick. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
