Child blocks in open-query-export query?

Questions & Help
,
1

Hello, I would like to export filtered view that we have for each page. I know it is not a thing and people recommend open-query-export plugin. I am trying to build a query that will give me page→block→children list when block has a tag. Something like

2024/08/01
Meeting One notes #projectA
point one
point two

2024/10/01
Meeting Two note #projectA
point uno
point dos

Default suggestion:

[:find (pull ?b [:block/content{(:block/page :as meta) [(:block/original-name :as title) (:block/journal-day :as sortKey)]}]):where[?b :block/refs ?p][?p :block/name “projecta”] ]

Does not give me children, but does give me pages.

2024/08/01
Meeting One notes #projectA
–
2024/10/01
Meeting Two note #projectA

How do I change query to include child blocks? Thanks.

2

When I use this:

#+BEGIN_QUERY
{:query [:find (pull ?b [*])
 :where
   [?b :block/refs ?p]
   [?p :block/name "projecta"]
 ]
}
#+END_QUERY

I get this:

image
image704×378 19 KB

If you need something different, please be more specific.

3

That’s what I get from the query when I run it in LogSeq, that does not allow me to export the data. When I put this into open-query-export plugin window it does not give me the same results. There is something else specific to open-query-export plugin that I need to specify to form the content of the message.

4

Maybe @benrhughes can give an idea.

5

When I use 'logseq.DB.datascriptQuery with [:find (pull ?b [*]) :where [?b :block/refs ?p] [?p :block/name “projecta”]] I also get the same thing as the plugin - only blocks that have the name directly. using block/path-refs allowed me to get all the blocks (including children), but the plugin does not organize them properly.