On Thursday, April 5, 2018 at 2:57:20 PM UTC-4, Lisandro wrote: > > Thank you Anthony, yes I'm aware of that. > I use it like that for this reason: sometimes (not very often) an external > app modifies a field of the auth_user table (specifically, it sets true or > false a field that I use as a flag). However that change isn't updated to > auth.user. In order to do so, the user needs to logout and login again. So > I retrieve the auth_user record again and store it to response.answer. > > Maybe it could be done like this: > if auth.is_logged_in(): > auth.user = db.auth_user[auth.user.id] > > But I thought it could be break something with Auth methods, so I store it > in response.user. >
Got it. Yeah, don't replace auth.user -- create a separate variable. > Anyway, I set this topic as "no action needed" because I opened a new > topic, I've found some more info and I think the issue isn't related to > that sentence. > But you indicated the select generated by that code was causing Postgres to hang. Are you sure that is the case? In other words, is the web2py code getting stuck at that line and ultimately causing your server to time out? Have you tried adding some logging statements to your code to determine exactly where it is getting stuck? Anthony -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
