Consider the graph below. I already talked about this graph when I wrote about permission-based graph queries.
In this post, I want to show off another way to deal with the same problem, but without using graph queries and using only the capabilities that we have in RavenDB 4.1.
