You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🤔 Yeah, I think it's more a bug. Search like that is converted to the jsonpath query value @? '$.vt.last_analysis_str ? @ <= 2024-07-07 because I assumed that range queries can be done only with numerical values. Unfortunately that assumption doesn't come with any validation.
If lexicographical compare works with jsonpath, I think it's just enough to add quotes and proper escapes when queried value doesn't look like a number (using jsonpath_quote -
Hey!
This might have been a change in the recent search refactoring, but this query for a string attribute results in an error:
However, comparing strings lexicographically does make sense in some cases. For example, if the strings are ISO 8601 format dates
The text was updated successfully, but these errors were encountered: