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
Describe your use case
I was attempting to filter on a custom metadata column for values that matched the form FOO___. I didn't initially know the filter was actually applying LIKE expressions to the SQL queries. Underscore is a wild card in LIKE expressions, so I was getting "incorrect" results back. Luckily, I am using Postgres for my backend so I could simply change the filter to FOO__ . Postgres deviates from the SQL standard regarding LIKE expressions without an explicit ESCAPE clause.
Describe the solution you'd like
Include the ESCAPE clause for operators that use LIKE expressions. Also update documentation to clearly reflect the need to escape , %, and _ when filtering to include those literal values.
Describe alternatives you've considered
Directly query the underlying tables in the database.
The text was updated successfully, but these errors were encountered:
Describe your use case
I was attempting to filter on a custom metadata column for values that matched the form FOO___. I didn't initially know the filter was actually applying LIKE expressions to the SQL queries. Underscore is a wild card in LIKE expressions, so I was getting "incorrect" results back. Luckily, I am using Postgres for my backend so I could simply change the filter to FOO__ . Postgres deviates from the SQL standard regarding LIKE expressions without an explicit ESCAPE clause.
Describe the solution you'd like
Include the ESCAPE clause for operators that use LIKE expressions. Also update documentation to clearly reflect the need to escape , %, and _ when filtering to include those literal values.
Describe alternatives you've considered
Directly query the underlying tables in the database.
The text was updated successfully, but these errors were encountered: