The problem is that it is not web2py but the user code that access the record. Web2py does not know that the user has been removed from the DB. This cannot be solved without checking if the user is still there and it can cause performance issues.
Suggestions? On Tuesday, 14 April 2015 11:29:37 UTC-5, Leonel Câmara wrote: > > Upon further investigation a way to cause a variant of this bug seems to > be: > > 1. Register and login with a user. > 2. Drop the user from the database (do not clean sessions) > 3. Try to logout the user created in 1 > 4. Have a ticket error because you have the session with the user but it > isn't in the database. > -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
