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
Textual values in "Data driven queryables" need to be enclosed in quotes manually when the values contain special characters (e.g. -), a requirement that may not be immediately apparent. Failure to do so can result in a parsing error that is not appropriately detected and managed:
Problem in fetching content for https://***.Error details, {"code":"UnexpectedToken","description":"Unexpected token Token('__ANON_4', 'c377') at line 1, column 23.\nExpected one of: \n\t* OR\n\t* PLUS\n\t* $END\n\t* STAR\n\t* MINUS\n\t* SLASH\n\t* AND\nPrevious tokens: [Token('INT', '6276')]\n"}
It would be helpful if the plugin automatically wrapped values in quotes behind the scenes when it appears to be necessary.
The text was updated successfully, but these errors were encountered:
The plugin generates distinct requests based on whether the value is enclosed in single or double quotes. When enclosed in single quotes, everything functions as anticipated. However, when enclosed in double quotes, the PostgreSQL index (I utilize PgSTAC) for the used property is bypassed, and the results are never passed to the plugin (because it takes forever).
⚠️ Enclosing a value in double quotes generates an SQL query that searches for a property with a name equal to the double quoted value, rather than searching for the specified value itself.
Textual values in "Data driven queryables" need to be enclosed in quotes manually when the values contain special characters (e.g.
-
), a requirement that may not be immediately apparent. Failure to do so can result in a parsing error that is not appropriately detected and managed:It would be helpful if the plugin automatically wrapped values in quotes behind the scenes when it appears to be necessary.
The text was updated successfully, but these errors were encountered: