I attempted to make it easier to use, mainly be having the connection and result pointers held as static data outside of R. For writing infrastructure and cross-db apps, DBI/RPostgreSQL is better. rpg might be preferred by some for interactive and lightweight applications. It fits more how I tend to interact with PostgresSQL. YMMV.
THK On Fri, Jul 25, 2014 at 11:52 AM, James David Smith < james.david.sm...@gmail.com> wrote: > Hi Tim, > > Thanks for bringing this to the attention of the community. I use R to > interact with PostgreSQL quite alot, so I've just been glancing at the > manual you've wrote. Nice work. I wonder though - what would you say > are the main advantages of using this over something like RPostgreSQL > which I use at the moment? > > Cheers > > James > > On 25 July 2014 17:45, Tim Keitt <tke...@utexas.edu> wrote: > > If you are interested in trying a new package for postgresql access, > take a > > look at 'rpg' (http://cran.r-project.org/web/packages/rpg/index.html). I > > wrote if primarily for my own use and for my students (rcpp + roxygen2 + > > rstudio now makes package writing ridiculously fast and painless). The > > design goal was convenience not generality so its not a replacement for > the > > DBI stuff. > > > > THK > > > > -- > > http://www.keittlab.org/ > > > > [[alternative HTML version deleted]] > > > > _______________________________________________ > > R-sig-DB mailing list -- R Special Interest Group > > R-sig-DB@r-project.org > > https://stat.ethz.ch/mailman/listinfo/r-sig-db > -- http://www.keittlab.org/ [[alternative HTML version deleted]] _______________________________________________ R-sig-DB mailing list -- R Special Interest Group R-sig-DB@r-project.org https://stat.ethz.ch/mailman/listinfo/r-sig-db
