Query Question: using unicode characters in querried properties doesn't seem to work

Questions & Help Queries
1

Hello, I have turned some time ago to a more “localized” statuses system based on unicode characters. For example, for TODO I am using [[🔳]] while for DONE I am using [[☑]]. They look different in different apps but in Logseq they look ok:

image

I was surprised to see that the following query which looks for the property value, returns nothing:

#+BEGIN_QUERY
{
:title [:h3 "DONE today:"]
:query (and (property current-status [[☑]])  (property touched <%today%> ) )
}
#+END_QUERY

while one that uses a text search returns properly:

#+BEGIN_QUERY
{
:title [:h3 "DONE today:"]
:query (and "☑"  (property touched <%today%> ) )
}
#+END_QUERY

What am I missing? I don’t understand why would it not work…

2

The first query works fine when I add:

current-status:: [[☑]]
3

as in:

#+BEGIN_QUERY
{
:title [:h3 "DONE today:"]
:query (and (property current-status:: [[☑]])  (property touched <%today%> ) )
}
#+END_QUERY

?

I get invalid query with that…

4

Not like that. I put it to the block of the task.

5

Yes, it does work like that. If I am inputting the status manually I get the correct result. Besides manual setting the property I am using the Inline Properties to “automatically” set the value of current-status property. I’ve tested some and found that it is consistently returning no values if I use {{p current-status, [[☑]] }}. Could the inline prop kit be confused by the unicode?

6

{{p current-status, [[☑]] }} works properly to me. I don’t see why the unicode character should cause an issue.

7

Me neither, I just don’t get it why there is no query result when i use inline prop versus typing the value manually. I have no idea how to troubleshoot this further…

Edit: what I find even stranger is that if I fill the current-status values by using inline prop kit, the results dissapear from the query. But, if I go and edit the current journal file with an external editor, say vscode, and save the file (even if I just added a space or whatever change) and re-run the query, it works… :-/ it’s baffling

8

In a heavily customized graph like yours, many things could be suspect. Try setting-up a new graph with minimal customization. If you narrow down to something, you may be able to share it for others to reproduce.