1. A computer implemented method for transparently interfacing an R client environment with a separate database engine environment, the method comprising: receiving, at a computer, an R language code fragment from the R client environment; analyzing the R language code fragment to identify a first group of R language constructs; determining computation resource requirements of at least one R language construct selected from among the first group of R language constructs; in response to the determination of the computation resource requirements, determining whether to map a first selected R language construct from among the first group of R language constructs to the R client environment or the database engine environment, wherein mapping of the first selected R language construct is based at least in part on volume of data operated upon by the first selected R language construct and security restrictions for communications of data between the R client environment and the database engine environment; and upon determining that the first selected R language construct should be mapped to the database engine environment, transforming the first selected R language construct into a database query language construct to be executed in the database engine environment, wherein execution of the database query language construct is subject to the security restrictions for communications of the data, execution of the database query language comprises: identifying the database query language construct that pertains to raw data for which a R client user does not have access to for security reasons; requesting execution of the database query language construct to access the raw data, wherein the raw data is processed at the database engine environment to generate processed data without providing the R client user direct access to the raw data; and sending the processed data to the R client user.