Skip to content
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

Forward compatibility with dbplyr 2.5.0 #265

Merged
merged 1 commit into from
Feb 24, 2024

Conversation

hadley
Copy link
Contributor

@hadley hadley commented Feb 21, 2024

I don't think there should be any other problems, but if you could run your tests with dev dbplyr installed, I'd certainly appreciate it.

I don't _think_ there should be any other problems, but if you could run your tests with dev dbplyr installed, I'd certainly appreciate it.
Copy link

codecov bot commented Feb 21, 2024

Codecov Report

Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (c23d816) 34.30% compared to head (6dfb3ac) 34.27%.

Files Patch % Lines
R/cte.R 0.00% 3 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #265      +/-   ##
==========================================
- Coverage   34.30%   34.27%   -0.04%     
==========================================
  Files          46       46              
  Lines        1775     1777       +2     
==========================================
  Hits          609      609              
- Misses       1166     1168       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@@ -15,7 +15,9 @@ get_tables_from_sql.lazy_select_query <- function(query) {

#' @export
get_tables_from_sql.lazy_base_remote_query <- function(query) {
if (inherits(query$x, "dbplyr_table_ident")) {
if (inherits(query$x, "dbplyr_table_path")) { # dbplyr >= 2.5.0
utils::getFromNamespace("table_path_name", "dbplyr")(query$x)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hadley table_path_name() seems to be exported from dbplyr 2.5.0. Should we just use dbplyr::table_path_name() instead?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can, but it will cause a R CMD check WARNING If you submit to CRAN before dbplyr 2.5.0 is released.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it. I will merge this in first and modify the function call when dbplyr 2.5.0 is released.

@jarodmeng jarodmeng merged commit cf31de7 into prestodb:master Feb 24, 2024
7 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants