> 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.

-- 

--- 
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.


Reply via email to