On Tuesday, May 31, 2016 at 4:24:20 AM UTC-4, Pierre wrote:
>
> I am trying to optimize things: I don't need to store anything in the
> session so I thought I could apply session.forget() once and that would be
> true for all application controllers functions
>
You must call session.forget() so
I am trying to optimize things: I don't need to store anything in the
session so I thought I could apply session.forget() once and that would be
true for all application controllers functions
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/
On Monday, May 30, 2016 at 6:56:30 AM UTC-4, Pierre wrote:
>
> Does *session.forget() *affects the way users
> login/logout/signup..etc ?
>
> should *session.forget() * be placed in every controller function or is
> there a way to apply it globally ?
>
Not sure what you're getting at with r
Does *session.forget() *affects the way users login/logout/signup..etc ?
should *session.forget() * be placed in every controller function or is
there a way to apply it globally ?
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (
oups.this was a bad idea. I will never do it again
I didn't know auth_user was so "ticklish" (especially under the arms)it
probably depends on the current user...
thanks Anthony
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/w
When a user is logged in, the user record (i.e., auth.user) is stored in
the session -- it does not get updated from the database on every request,
as that would require too many database hits. It will be updated the next
time that user logs in.
Anthony
On Sunday, May 29, 2016 at 2:43:02 PM UT
6 matches
Mail list logo
