Re: where is 'request' as in from x import y

On May 27, 10:58 am, MikeKJ wrote: > Interesting, I thought I was doing that in my save method but obviously I > cant be. Of course it can't. The request only exists when there's an actual HTTP request sent to your HTTP server. Your model code is (hopefully) totally independant and unaware of the

Re: where is 'request' as in from x import y

Interesting, I thought I was doing that in my save method but obviously I cant be. example. Model 1: auth_user_id row_id_of model_being_saved timestamp Model 2: something def save(self): auth_user_id = request.user.id row_id_of_model_being_saved = something Model

Re: where is 'request' as in from x import y

On Thursday, May 26, 2011 12:52:28 PM UTC+1, MikeKJ wrote: > > > Is this really only available to a view? All I want is to know is the auth > user id currently logged in so I can save it into another model, has to be > in the model so it is part of the admin save method You can't access something

Re: where is 'request' as in from x import y

Is this really only available to a view? All I want is to know is the auth user id currently logged in so I can save it into another model, has to be in the model so it is part of the admin save method MikeKJ wrote: > > I need to get the auth user id in a save method on a model so > > from dja

Re: where is 'request' as in from x import y

The request object is passed to the views in your views.py you have mapped to in your urls.py Do you understand the layout of a basic django project? A python module is not executed to handle a request, but is imported at the startup of the process and your view functions are called depending on t

where is 'request' as in from x import y

I need to get the auth user id in a save method on a model so from django.contrib.auth.models import User user_id = request.user.id the error comes back as name 'request' is not defined Cheers -- View this message in context: http://old.nabble.com/where-is-%27request%27-as-in-from-x-import