Yes, as Massimo and I have suggested, you should store them in extra_fields. That way they will be associated with the users. Another alternative is to use an extra cookie, but that seems like a waste of bandwidth.
On Friday, May 23, 2014 9:06:12 PM UTC-7, Mandar Vaze wrote: > > Derek, > > May be I misrepresented my scenario - These aren't exactly preferences. > In both the applications - user sees SQLFORM.grid with large number of > records. User will use filter to reduce the count. > Depending on the user - user is likely to use same filters for quite some > time - across logins/logouts > So these aren't exactly preferences. > > I understand that using sessions across login/logout isn't the right thing > to do - but since I got that behaviour in 2.3.2 - I want it in current > version as well :) > Also - the kind of information I'm storing shouldn't lead to "security > issue" AFAIK > > What Anthony suggested is helpful. > > >> If you are storing preferences in user accounts then you should store >> them with the user accounts >> > > Can you provide additional details ? Do you mean auth.settings.extra_fields > ? > > -Mandar > > -- 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.
