although stored into the database, the membership information is carried along within the session. I don't see a reason to bring around the same data twice... if the reason behind is just "logic", then it doesn't make sense to duplicate the data. If the reason is serious reporting/datamining/complex queries/etc than I don't see the additional joins to find the membership much difficult to add....
On Wednesday, June 25, 2014 8:08:17 PM UTC+2, Carlos Zenteno wrote: > > I am classifying my users within groups (ie, carpenters group) but I am > wondering > if it would be useful or more efficient to also add a field in auth_user > (ie, is_carpenter). > > Would it be faster to check the is_carpenter flag in the db or to do it > from the auth > system checking the membership of the user to the group? > > Would it be better to do both? use the group to restricting functions and > check > the field for other logic? > > thanks... > -- 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.
