Simon Urbanek

@robchallen I don't see how the initialisation etc has anything to do with the double-wrapping, since that is done by the package and the constructor, not R6. R6 is just...

@robchallen All memory management is automatic, the references are mirrored between the languages, i.e., an object on one side is released when its reference is released on the other side....

There are two problems here and those are the main reason why this is not supported and why it wouldn't work in most cases even if rJava allowed it. First,...

@jeroenooms yes, the only reliable way to terminate the JVM is via `System.exit()` which kills the entire process (including R itself). As for `unload`, in principle that would get us...

No, because rJava doesn't own those references. Except for a few internal objects rJava releases all references to objects created through its API, so they get released by R if...

Yes, you should really set `java.parameters` in your startup scripts such that it is always active. That said, I think you don't actually need it for RJDBC - you only...

Sure, it's relatively easy to have separate processes. However, the point of rJava is exactly to NOT have a separate process, otherwise you could have used Rserve, SNOW or anything...

While trying to address #334 I have now final proof that it is impossible to truly unload or even re-initialize a VM. I have implemented a fully clean approach ([just...

First, please try it in R since there have been issues reported in some versions of RStudio (if it is an issue in RStudio please check their support). If the...

Duplicate of #90. I guess an option to `fetch` would be possible. My main concern is that we don't want to lose precision inadvertently - that's a lot worse than...