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
If I run dbc_init(..., "my_db"), it sets variables for tables like my_db_public_some_table.
This happens for all tables that exist when I run dbc_init and is super handy!
However, if I add tables after running init, then they won't show up until I re-run the dbc_init(...) command.
WDYT of adding a helper like my_db_init()? That way, users have this handy workflow
dbc_init(some_conn, "my_db")
# Create a table ----# using execute
my_db_execute(...)
# or using dplyr
copy_to(dbc_init_src(), mtcars, "mtcars")
# Re-init and view new table ----
my_db_init()
# now, my_db_<TAB> gives my_db_public_mtcars
In practice, re-running dbc_init(my_db_src()$con, "my_db") isn't too bad, but I seem to run it a lot to keep things "in sync"!
The text was updated successfully, but these errors were encountered:
If I run dbc_init(..., "my_db"), it sets variables for tables like
my_db_public_some_table
.This happens for all tables that exist when I run dbc_init and is super handy!
However, if I add tables after running init, then they won't show up until I re-run the dbc_init(...) command.
WDYT of adding a helper like
my_db_init()
? That way, users have this handy workflowIn practice, re-running
dbc_init(my_db_src()$con, "my_db")
isn't too bad, but I seem to run it a lot to keep things "in sync"!The text was updated successfully, but these errors were encountered: