First of all, I want to thank this great community!
I’ve learned so much about Logseq, and it became my only tool for work and personal life.
I think that Datalog is the most powerful tool I’ve seen in a KT system, and it’s a game changer. Writing information is easy; the challenge is to retrieve it.
For this reason, I want to master Advanced Queries, which have quite a steep learning curve .
I’ve been searching around for days without finding a way of doing what the following:
Inside journals, I’m using blocks to keep track of meetings. Meetings have multiple properties:
In addition to the questions from @mentaloid
It is a good idea to define property values with comma separation and in config say to process them as pages.
This makes fetching the data easier in queries.
Hi, thank you for the help and sorry for my late reply
yes, with the Simple Queries I’m all good. I know simple queries can be used within advanced queries, but my goal is to get used to the Advanced Queries
By enabling that option, would it mean I should search the participants by refs instead of by text?
If yes, in a mixed case like the one below, Donal Duck doesn’t have a page. How can I find the meetings with him as a participant?
From the DB schema, there is the following comment in the code (github link). Does it mean that I need to search Donald Duck by text?
Easier. The option enables all to be interpreted as page. So you don’t need the [[ ]] anymore and all will be retrievable using :block/refs.
For example I use the property “onderwerp” (subject) in this manner.
PKM only exists in the value of this property: onderwerp:: PKM
And I can use this query regardless. To find all the blocks that have this subject. Because it is still a page thanks to that config option.