I have a query that works:
{{query (and (property client “Superclient”)(property month [[01-07-2022]]))}}
I then wanted to add one more term to be more specific in my results:
{{query (and (property type “activity”)(property client “Superclient”)(property month [[01-07-2022]]))}}
This brings Logseq crashing down. No results, just a blank block, then everything hangs and becomes totally unresponsive. I have to force kill Logseq after this to get it working again.
Is that a bug or am I abusing the ‘and’ operator here? If it’s a user-error, shouldn’t there be a more graceful way of letting me know I’m doing it wrong?