Why do you want to change the request object? Why are you trying to store a user object? Perhaps you want to store it in a session? I think you should explain what you are trying to do.
Dougal --- Dougal Matthews - @d0ugal http://www.dougalmatthews.com/ 2009/3/31 Masarliev <m.masarl...@gmail.com> > > yes it's bad idea. other solution is to create additional object > similar to request.user for example request.additional. How can i do > that. > > On Mar 31, 4:17 pm, Jeff FW <jeff...@gmail.com> wrote: > > Changing request.user.id doesn't make sense--that would be trying to > > change the id of the user object itself. I think what you're trying > > to do is change the user that is actually logged in... right? If > > that's true, then you need to set request.user *not* request.user.id-- > > but that seems like a very bad idea, and it won't (I think) change it > > in the session. What are you trying to accomplish? > > > > -Jeff > > > > On Mar 31, 2:35 am, Masarliev <m.masarl...@gmail.com> wrote: > > > > > I have a application but i have error in base logic and I need to > > > change request.user.id. > > > Is it posible to do that > > > I tried request.user.id = ???? but with no result > > > --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
