fraud detection
Have you figured out a way to add columns to DuckDB from R vectors? I'm not sure this is possible yet without using inefficient insert operations. Ideally, I'd like to pull in some columns from the DB, generate a new…
when indexing you can always pass `drop=FALSE` to prevent returning a vector. It will always return a matrix or data.frame.
Base R is fine. I would much rather not include the tidyverse and all of its transitive dependencies.
options(error=recover)
Yeah, that's a valid point. And it took me a couple years to internalize these differences -- mostly by being burned on numerous occasions. Base R has a lot of idiosyncrasies and they have to be memorized,…
I use a simply device to keep these straight: - (l)apply: List apply always returns a list - (s)apply: simplify apply tries to return simplified result - (v)apply: verify apply checks the return type conforms to user…
fraud detection
Have you figured out a way to add columns to DuckDB from R vectors? I'm not sure this is possible yet without using inefficient insert operations. Ideally, I'd like to pull in some columns from the DB, generate a new…
when indexing you can always pass `drop=FALSE` to prevent returning a vector. It will always return a matrix or data.frame.
Base R is fine. I would much rather not include the tidyverse and all of its transitive dependencies.
options(error=recover)
Yeah, that's a valid point. And it took me a couple years to internalize these differences -- mostly by being burned on numerous occasions. Base R has a lot of idiosyncrasies and they have to be memorized,…
I use a simply device to keep these straight: - (l)apply: List apply always returns a list - (s)apply: simplify apply tries to return simplified result - (v)apply: verify apply checks the return type conforms to user…