[R-sig-DB] RMySQL and RPostgreSQL interaction

[NISHIYAMA Tomoaki]

Hi,

It is a pity that such interference between different database driver happens.
We can exclude export of dbObjectId from RPostgreSQL, but I reallized that would 
cause a warning on TSPostgreSQL. 
One of the possible solution may moving the definition of db* to DBI and exclude from
individual database drivers.  Other routines that may be imported to DBI includes
dbBeginTransaction(), now deleted from RPostgreSQL, but some request are coming.

DBI is last published on 2009-12-22, but not changed thereafter.
http://cran.r-project.org/web/packages/DBI/index.html
Author:	R Special Interest Group on Databases (R-SIG-DB)

So, it appears the DBI can be updated based on discussion on this mailing-list.
But I do not know how do we make agreement and update.

Best regards,

On 2012/09/19, at 0:40, Paul Gilbert wrote:

> I am doing some comparison for which I load both RMySQL and RPostgreSQL from my own packages TSMySQL and TSPostgreSQL and I am getting the following warning building a vignette. I think with package namespaces / S4 definitions it is a bit difficult to generate a self contained example, at least I have not yet managed to do that, but I would appreciate any suggestions about what needs to be done.
> 
> Loading required package: TSPostgreSQL
> Loading required package: RPostgreSQL
> Warning in .simpleDuplicateClass(def, prev) :
>  A specification for class "dbObjectId" in package 'RPostgreSQL' seems equivalent to one from package 'RMySQL' and is not turning on duplicate class definitions for this class
> 
> (I'm using  R version 2.15.1 on Ubuntu.)
> 
> Thanks,
> Paul
> 
> _______________________________________________
> R-sig-DB mailing list -- R Special Interest Group
> R-sig-DB using r-project.org
> https://stat.ethz.ch/mailman/listinfo/r-sig-db