It's not uncommon for me to get eyes to big for my laptop's stomach and try to dbGetQuery some table that's too big for rJava to handle (as configured).
Usually it's the case then that the Java heap gets a bit clogged up and could benefit from a gc(); I recently came upon this Q&A about how to gc() specifically on the Java side; it could be useful to expose a helper function in RJDBC to handle this like
For my own purposes, I'm writing a package that currently has an RJDBC import but no direct rJava import -- could avoid cluttering the DESCRIPTION a bit more if I can importFromRJDBC instead of rJava.
But I do think that this operation is common enough for RJDBC use cases specifically that exposing this helper here makes sense.
It's not uncommon for me to get eyes to big for my laptop's stomach and try to
dbGetQuery
some table that's too big forrJava
to handle (as configured).Usually it's the case then that the Java heap gets a bit clogged up and could benefit from a
gc()
; I recently came upon this Q&A about how togc()
specifically on the Java side; it could be useful to expose a helper function inRJDBC
to handle this likeFor my own purposes, I'm writing a package that currently has an
RJDBC
import but no directrJava
import -- could avoid cluttering theDESCRIPTION
a bit more if I canimportFrom
RJDBC
instead ofrJava
.But I do think that this operation is common enough for
RJDBC
use cases specifically that exposing this helper here makes sense.Happy to file a PR if you think it's useful.