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
RPostgreSQL column names regression #516
Comments
Can you use RPostgres instead? |
That's what I've done for the vignette that caught this, so {dittodb} is fine without a fix for this. |
It probably is too aggressive to just break this though. I think we should just restore the previous method. |
I'm happy to send a PR that does that. |
That would be great, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've been testing the development branch of dbplyr and I believe there might be a regression with RPostgreSQL backends: it appears the column names are not being added to the
ops
of thetbl
object so subsequent verbs that reference those columns (select()
) don't work.I believe this is related to removing the special-case
db_query_fields.PostgreSQLConnection()
called fromtbl_sql()
. I'm happy to submit a PR that brings backdb_query_fields.PostgreSQLConnection()
or try a different approach.The text was updated successfully, but these errors were encountered: