Convenient queries with property values as input?

Questions & Help Queries
1

Hi all,

I use complex queries in logseq to search for strings in my meeting notes, for example.

It is inconvenient to always open the query code to change the strings, that are used as input.

Therefore, I am curious if it is possible to connect values outside of the query with the input variables. This could be page properties of a known page or block content of a block with a known UUID.

Porperty on Testpage

image
image825×124 4.66 KB

Example Query:

#+BEGIN_QUERY
{:title "Suche alle Blöcke, die einen Suchbegriff enthalten"
 :inputs ["Testbegriff"]
 :query [:find (pull ?b [*])
         :in $ ?string1
         :where
         [?b :block/content ?c]
         [(not= ?string1 "")]
         [(re-pattern ?string1) ?q]
         [(re-find ?q ?c)]]
 :collapsed? false}
#+END_QUERY

Do you know how I can use the value of the property “string1” on “Testpage” as input value for the variable “string1” in my query?

2
  • Cannot pass it in :inputs
  • But can read it at the beginning of :where , e.g.:
    [?p :block/original-name "Testpage"]
[?p :block/properties ?props]
[(get ?props :string1) ?string1]
    • This approach covers the majority of needs.
      • Some complicated values cannot be produced in Datalog, they need scripting.
1 Like
3

Perfect, thanks a lot. The query now looks as follows:

#+BEGIN_QUERY
{:title "Suche alle Blöcke, die einen Suchbegriff enthalten"
 :query [:find (pull ?b [*])
         :where
         [?p :block/original-name "Testpage"]
         [?p :block/properties ?props]
         [(get ?props :string1) ?string1] 
         [?b :block/content ?c]
         [(not= ?string1 "")]
         [(re-pattern ?string1) ?q]
         [(re-find ?q ?c)]]
 :collapsed? false}
#+END_QUERY

It finds all blocks that contain a string that is defined in the page property “string1” of “Testpage”. The property is forbidden to be empty to not query all block.

4

I tried doing the same in DB version but it doesn’t work, I think block/properties and block/original-name are named differently ind DB version? When I look at block EDN data I see the string1 property but with a more complex key like so: “:user.property/string1-K1yBJFiz”

How can I make it work in DB version?

5

Welcome.

  • I’m not experienced in the DB version.
  • The block’s EDN data are indeed different, but should be followed no matter.
    • The following will probably break in the future, but for now it seems to work:
      [?p :block/title "Testpage"]
[?b :user.property/string1-K1yBJFiz ?p]
6

Thanks for your help, I tried to merge that with Gregor83’s query above without sucess. I think one of the issue might be that [?p :block/title “Testpage”] can match all blocks instead of just pages.

7
  • Here is what worked to me:
    {
 :query [:find (pull ?b [*])
     :where
         [?p :block/title "Testpage"]
         [?p :user.property/string1-K1yBJFiz ?prop] ; replace with own property name
         [?prop :block/title ?string1]
         [?b :block/title ?c]
         [(not= ?string1 "")]
         [(re-pattern ?string1) ?q]
         [(re-find ?q ?c)]
 ]
}
  • Can also replace the last three clauses with this one:
    [(clojure.string/includes? ?c ?string1)]
  • To match only pages, replace the first clause under :where with this one:
    [?p :block/name "testpage"]