ah! I'm setting and retrieving the value via json using two @service.jsonrpc functions.
Have I found a hole? or should I be adding a little more code within my json "setter" function? On 16 June 2011 16:57, Massimo Di Pierro <massimo.dipie...@gmail.com> wrote: > That's automatic. If you just do > > auth.user.tag = 'new value' > > than the new value is stored in the session and retrieved at next http > request > > On Jun 16, 10:19 am, Carl <m...@carlroach.com> wrote: > > thanks. a little detail needed: given my extra field is called 'tag' > > can I change its value like: > > > > session.auth.user.tag = 'new value' > > > > but then how do I get the session to update the cookie ready for the > > next browser load/refresh? > > > > On Jun 16, 2:46 pm, Massimo Di Pierro <massimo.dipie...@gmail.com> > > wrote: > > > > > > > > > > > > > > > > > the logged in user is stored in session.auth.user so yes, if you > > > change the user info in db, you will not see the change in > > > session.auth.user until you reload. You need to change the info in > > > both places. > > > > > On Jun 16, 5:17 am, Carl <m...@carlroach.com> wrote: > > > > > > In db.py I've added fields to table_user_name > > > > > > My code updates one of these 'extended' fields with update_record(). > > > > The code also accesses auth.user.<fieldname> but I think these values > > > > get populated from a cookie. > > > > > > a) is it true that a cookie is used > > > > > > b) if a) is true, how to I refresh the cookie? > > > > > > c) if b) isn't true, where am I going wrong? >
