Here's my key usage scenario, which makes Arango always teeter in and out of for my needs. Every document has a rights object. Each rights object has the groups that can perform a CRUD operation against it. So if I want to find all of the documents a user can read, the query would involve looking the user up, by their key, then using that in the FILTER to the affect user.groups[*] IN d.rights.readers[*].
Base on the conversation above, sure, I can do a DB read outside of the AQL to get the user's groups, expand the filter myself using params and string build, then have the AQL engine execute the second half of the query. My trouble with this is that it makes the code much more complex (with more network transactions since I have to hit Arango twice) than the relatively simply AQL to first LET u = FIRST(blah), then join. -- You received this message because you are subscribed to the Google Groups "ArangoDB" 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.
