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.

Sign up for GitHub

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

Jump to bottom

investigate whether {dbplyr} is required for SQLite exports #105

Closed

cjyetman opened this issue Feb 9, 2024 · 0 comments · Fixed by #106

Assignees

Member

cjyetman commented Feb 9, 2024

data_prep-1  | INFO [2024-02-09 08:15:25] Formatting and saving file: "entity_info.sqlite".
data_prep-1  | Error in check_dbplyr() : 
data_prep-1  |   The package "dbplyr" is required to communicate with database backends.
data_prep-1  | Calls: <Anonymous> ... copy_to.DBIConnection -> check_dbplyr -> check_installed

AlexAxthelm self-assigned this

cjyetman mentioned this issue

add dbplyr dependency #106

Merged

cjyetman closed this as completed in #106

cjyetman added a commit that referenced this issue


          add dbplyr dependency (#106)

58cdce5

closes #105

To be honest, I don't fully understand why {dbplyr} is needed, but it
appears that something in this code requires it...


https://github.com/RMI-PACTA/workflow.data.preparation/blob/c08b8fb5a139716997ae2c0e83a01757d51a9a2d/run_pacta_data_preparation.R#L687-L707

I have verified that adding it allows the Docker run with SQLite export
to complete successfully (without the error).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment