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
Is your feature request related to a problem? Please describe.
I let user search for words in his records and preview what has matched. So for example if he has a record with title of "Hello World" and he writes "world", Cubejs will return the record as it's case insensitive. However, after the user reviews returned records he can confirm selecting them, and this happens on my backend. By definition, my backend has to treat user search with respecting the case.
So after user confirm his query, he's surprised that saved records are empty cause "world" does not match "Hello World".
Describe the solution you'd like
I would like to pass an option to contains and notContains filter to force LIKE or ILIKE.
If you are interested in working on this issue, please leave a comment below and we will be happy to assign the issue to you.
If this is the first time you are contributing a Pull Request to Cube.js, please check our contribution guidelines.
You can also post any questions while contributing in the #contributors channel in the Cube.js Slack.
Is your feature request related to a problem? Please describe.
I let user search for words in his records and preview what has matched. So for example if he has a record with title of "Hello World" and he writes "world", Cubejs will return the record as it's case insensitive. However, after the user reviews returned records he can confirm selecting them, and this happens on my backend. By definition, my backend has to treat user search with respecting the case.
So after user confirm his query, he's surprised that saved records are empty cause "world" does not match "Hello World".
Describe the solution you'd like
I would like to pass an option to
contains
andnotContains
filter to forceLIKE
orILIKE
.Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: