Are subqueries possible in Logseq?

This is exactly why I wrote this proposal to use properties as indications to traverse the graph and present that tree structure in different ways:

We could even concatenate more properties:: as indications, for example genre::, year:: and artist:: to browse music albums starting from genre folders, then years and then by artist:

{{tree genre year artist}}
{{folders genre year artist}}

to print an indented list or folders and subfolders.

This way you define one time the best way to browse a certain part of your graph and use it multiple times instead of writing complex queries everytime you are looking for something.

The browsing experience would be as natural as using a file manager.