You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since upgrading to dbplyr 2.4.0, we receive the below warning message when setting up a table variable, even though we are using in_schema as suggested by the warning. This warning only occurs when we use the pool package to manage our database connection. In contrast, the same code, when utilizing DBI for connection management, emits no warning.
library(tidyverse)
library(pool)
conn<-pool::dbPool(odbc::odbc(), .connection_string="{MY MSSQL CONN STRING}")
my_table<- tbl(conn, dbplyr::in_schema("MySchema", "MyTable"))
#> ℹ Using `ident_q()` for a table identifier is intended as fallback in case of#> bugs.#> ℹ If you need it to work around a bug please open an issue#> <https://github.com/tidyverse/dbplyr/issues>.#> It looks like you tried to incorrectly use a table in a schema as source.#> ℹ If you want to specify a schema use `in_schema()` or `in_catalog()`.#> ℹ If your table actually contains "." in the name use `check_from = FALSE` to#> silence this message.#> This message is displayed once every 8 hours.
Since upgrading to dbplyr 2.4.0, we receive the below warning message when setting up a table variable, even though we are using
in_schema
as suggested by the warning. This warning only occurs when we use thepool
package to manage our database connection. In contrast, the same code, when utilizingDBI
for connection management, emits no warning.Created on 2023-11-27 with reprex v2.0.2
Session info
The text was updated successfully, but these errors were encountered: