Awesome! Thanks, that does exactly what I need.
Shawn
On Jan 29, 2010, at 12:08 PM, tom wrote:
> maybe that middleware can help you out with getting the username
> http://code.djangoproject.com/wiki/CookBookThreadlocalsAndUser
--
You received this message because you are subscribed to the Goo
This is much better than my ramblings.
On Fri, Jan 29, 2010 at 12:08 PM, tom wrote:
> maybe that middleware can help you out with getting the username
> http://code.djangoproject.com/wiki/CookBookThreadlocalsAndUser
>
> On 29 Jan., 18:05, Shawn Milochik wrote:
>> I need to implement auditing for
If worse comes to worst, you could always patch the url dispatcher to
store the user in a global variable before it calls the view. It
should be sure to set that variable to None when the view returns, so
that the global doesn't keep a reference on the user object between
requests (a try finally a
maybe that middleware can help you out with getting the username
http://code.djangoproject.com/wiki/CookBookThreadlocalsAndUser
On 29 Jan., 18:05, Shawn Milochik wrote:
> I need to implement auditing for my models. The current plan is to listen for
> the post_save() signal and dump the current v
I need to implement auditing for my models. The current plan is to listen for
the post_save() signal and dump the current values of the instance to an
external database.
The only problem is that I need to store the request.user with this data, and I
don't see any way to capture that, since it
5 matches
Mail list logo
