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
I find that I increasingly use DuckDB with dbplyr and parquet for persistence. In the development version of my R package farr, I recently added a function duckdb_to_parquet() that implements this idea (source code here).
Basically, I can pass a lazy query object to the function and it will save it as a parquet file. Very slick.
I have a little note demonstrating use of this function here (see pages 8 and 9).
Maybe something similar would make sense for the duckdb R package. (Note that the schema argument to my function may not make sense, I use this to organize my parquet files so that I can use them much like I would use a PostgreSQL database.)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I find that I increasingly use DuckDB with
dbplyrand parquet for persistence. In the development version of my R packagefarr, I recently added a functionduckdb_to_parquet()that implements this idea (source code here).Basically, I can pass a lazy query object to the function and it will save it as a parquet file. Very slick.
I have a little note demonstrating use of this function here (see pages 8 and 9).
Maybe something similar would make sense for the
duckdbR package. (Note that theschemaargument to my function may not make sense, I use this to organize my parquet files so that I can use them much like I would use a PostgreSQL database.)Beta Was this translation helpful? Give feedback.
All reactions