On Tuesday, April 9, 2013 11:30:20 PM UTC+2, Alan Etkin wrote: > > > well, you should have for every record on mongo a copy of groups, > membership and > > auth_user if you want to do that "in one shot". > > Seems like it involves a lot of extra data stored and also possible sync > problems, i.e. reading old rbac information
> > The other way is having a transaction scanning groups, membership and > auth_user and > > cross-reference it with the "FK" of your table.... > > This one looks like a better approach. I suppose it means adding actual db > queries before performing the query to filter, with a considerable increase > of server usage for each filter. > > Unfortunately with no joins either you store within your record the relevant FK object and "update" them as soon as the FK changes, or you have to resort to fetching every "joined table" in a separate step. Wouldn't know about concurrency issues, but for an "accessible query" with no joins basically you have to fire at least 3 queries (or 4, depending on the auth_user records being available yet, e.g. in a session) - membership - permission - end table with the everybody_group_id logic, probably other 2 queries. -- --- 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/groups/opt_out.
