-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Ignoring case with remote database table filter operations #3783
Comments
You will need to generate the needed SQL by hand (i.e. relying on the SQL fall back translations). There's unfortunately no way that dbplyr can translate every stringr feature into every database backend. |
Fair enough, thanks Hadley. I'll explore the suggestions received in SO. |
Perhaps this should be closed, for now I'll just move it to dbplyr |
This issue was moved by romainfrancois to tidyverse/dbplyr#150. |
This issue was moved by romainfrancois to tidyverse/dbplyr#151. |
This old issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with reprex) and link to this issue. https://reprex.tidyverse.org/ |
I've detailed this question on this SO page.
I can't figure out how to apply a non-case-sensitive filter query to a remote PostgreSQL table using
dplyr
. To demonstrate:To ignore case
stringr::fixed('Setosa', ignore_case=TRUE)
works with tibble filtering. But with the postgres table it has no effect:Is there any way around this, or possibly dev plans to accommodate the
ignore_case
arguments orfixed()
orregex()
for database table filtering?The text was updated successfully, but these errors were encountered: