Make block and page references consistent (`path-refs` in advanced queries)

Feedback Feature Requests
1

Please make advanced queries for block and page references behave the same with regards to :block/path-refs.
The idea is to to gradually make blocks and pages consistent, so that they can be used interchangeably in queries.

More details

Let’s take an example - find all blocks that have links my page:

# test case.md
- b1 of test case with link to [[my page]]

# my page.md
- b1 of my page
- b2 of my page

{{query [[my page]] }}

would be able to find all three blocks. This is great, because we asked for blocks that link to my page, but also can find content inside my page itself! More technically, contained blocks of my page inherit a link reference to this page, which is added in :block/path-refs.

OK, let’s try to add a block reference.

# my page.md
- my block
  id:: 1234
  - child 1

and reference it somewhere:

# test case.md
- ((1234))

Using advanced queries here, as simple queries (TMK) have no way to query blocks:

{
:query [:find (pull ?b [*])
    :where
        [?br :block/uuid #uuid "1234"]
        [?b :block/path-refs ?br]
]
}

In contrast, this will only find the “outside” block link in test case, not child 1 (or other child blocks of my block).

In my book, these two cases would be equivalent, but currently are treated not consistently.
I’d image, this decision been driven by performance reasons - if so, might this be solved by a more database-driven Logseq approach?

There is a workaround for the block case query. But I think a more uniform approach would be beneficial, especially for people seeking more block-level experience. Thanks!

2

Can you please share the workaround you are referring to?
Will it help with querying child blocks with to do tags that have no block refernce tags but its parent block has tags with block references?

3

If it’s super important to you, I’d need to search in second brain. But never used it in practice, as too complicated for daily needs.