-
Notifications
You must be signed in to change notification settings - Fork 32
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
<Pool> uses an old dbplyr interface warning (and e.g. error when using stringr) #132
Comments
I see in the
Which I suspect is what is indirectly causing the |
I am getting this error as well. All i did to generate this error was the following:
|
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
I'm also getting the warning:
Any updates on this? Should one be concerned about this warning when using |
You don't need to concerned about the warning, and it's fixed in #152. Hopefully we can get a pool release out in the next week or so. |
Now replaces minimal set of methods with automatically generated wrappers. Fixes #132
Due, I believe, to
dbplyr
latest update on CRAN I am receiving a warning and errors in my scripts (as well as in a CRAN package I maintain) that relies onpool
.The warning seems to appear even with common filters. The error appears in filters that used to work fine until the
dbplyr
update, but that perhaps did not have a fully compliant syntax to begin with.Reprex below should show the issue. Latest version on CRAN and current development version from the repository show the same behaviour.
Created on 2022-06-06 by the reprex package (v2.0.1)
Session info
The text was updated successfully, but these errors were encountered: