Skip to content

dbplyr 2.4.0- breaking changes #1416

@kelseyroberts

Description

@kelseyroberts

With the updates to dbplyr version 2.4.0 it seems like some of the arguments that worked in the previous version, I was using version 2.3.2, no longer work.

The 3 main differences we are seeing is

  1. The "database" argument needs to be called “catalog” now
  2. "schemaname" needs to be called “schema”
  3. "tablename" needs to be called “table”

Database to catalog
For example this call used to work with the argument “database”:

database_connection_object%>%
  tbl(DBI::Id(
    database = "db1",
    schema = "schema1",
    table = "table1"
  )) %>%
  collect()

This now requires “database” to be named “catalog” as seen below:

database_connection_object%>%
  tbl(DBI::Id(
    catalog = "db1",
    schema = "schema1",
    table = "table1"
  )) %>%
  collect()

Schemaname and Tablename
“schemaname” and “tablename” were arguments that worked before and are now also giving errors:

database_connection_object%>%
  tbl(DBI::Id(
    database = "db1",
    schemaname = "schema1",
    tablename = "table1"
  )) %>%
  collect()

schemaname and tablename now are required to be “schema” and “table”:

database_connection_object%>%
  tbl(DBI::Id(
    database = "db1",
    schema= "schema1",
    table= "table1"
  )) %>%
  collect()

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugan unexpected problem or unintended behavior

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions