-
-
Notifications
You must be signed in to change notification settings - Fork 384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
contains() doesn't return hits for matched fields that have only one value? #88
Comments
As a side note, you don't need Does
work? I feel like it should work (since a string trivially contains itself). |
Negative. The actual query (without
"foo" etc in the example above are actually File A:
File B:
The query in
What the query in
If I change File A to look like this:
Then the query in
As expected. But it implies that if I expect to add more than a single value to any field in the future then I should make all fields Hope that is more clear. Thanks. |
Ah, is this operating over links? I understand what's going on then, I think - I will modify this so that |
Yes it is operating over links. Thanks. |
Fixed in upcoming release 0.2.10. |
I'm experiencing this behavior again in the current version 0.2.14. Some files have:
Others have:
This query only returns notes that have the list, and does not return notes that have
This query only returns notes that have the strict equality
|
For v0.5.47, I also had a similar issue and found that adding quotes around the link allowed it to be queried by the contains function. Try putting double quotes around the link for the case where there is a single link: The query with the contains function should then return both cases. In the documentation, it says
|
@davecan OR the two ideas together? I wonder if it's a type mismatch. If so, you can use |
File A:
File B:
This query returns only A as expected, because it is matching a string vs a list:
This query only returns B which is unexpected:
Intuitively I would expect the above query to return both A and B. But maybe I'm missing something in how it works.
The text was updated successfully, but these errors were encountered: