[web2py] Re: auth.user_groups are cached? Can't see changes beeing done in admin UI until user logout/login again

2013-07-30 Thread Massimo Di Pierro
Yes they are cached. You can call auth.update_groups() at every request to make sure the groups are updated but this is a lot of extra DB IO. On Tuesday, 30 July 2013 08:55:13 UTC-5, David Marko wrote: auth.user_groups are cached? Cant see changes beeing done in admin UI until user

[web2py] Re: auth.user_groups are cached? Can't see changes beeing done in admin UI until user logout/login again

2013-07-30 Thread Anthony
On Tuesday, July 30, 2013 10:49:29 AM UTC-4, Massimo Di Pierro wrote: Yes they are cached. You can call auth.update_groups() at every request to make sure the groups are updated but this is a lot of extra DB IO. Maybe use the DAL table callbacks to call auth.update_groups() only when

[web2py] Re: auth.user_groups are cached? Can't see changes beeing done in admin UI until user logout/login again

2013-07-30 Thread David Marko
But update_groups do update only for just login user so callbacks should do the work for every user, and this probably cant be done ... -- --- You received this message because you are subscribed to the Google Groups web2py-users group. To unsubscribe from this group and stop receiving

[web2py] Re: auth.user_groups are cached? Can't see changes beeing done in admin UI until user logout/login again

2013-07-30 Thread Anthony
Oops, sorry, wasn't thinking. I suppose you could do something more sophisticated like store the affected user IDs in cache.ram and do a check there on each request. Anthony On Tuesday, July 30, 2013 1:28:13 PM UTC-4, David Marko wrote: But update_groups do update only for just login user so