Re: [R-sig-DB] RMySQL and RPostgreSQL interaction

[Prof Brian Ripley]

On 19/09/2012 03:33, NISHIYAMA Tomoaki wrote:

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.



Not so: CRAN packages can only be updated by their maintainer (Cc:ed here).

If David James does not want to update DBI, he maybe could be persuaded 
to hand over the maintainership.


--
Brian D. Ripley,  rip...@stats.ox.ac.uk
Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
University of Oxford, Tel:  +44 1865 272861 (self)
1 South Parks Road, +44 1865 272866 (PA)
Oxford OX1 3TG, UKFax:  +44 1865 272595

___
R-sig-DB mailing list -- R Special Interest Group
R-sig-DB@r-project.org
https://stat.ethz.ch/mailman/listinfo/r-sig-db

Re: [R-sig-DB] RMySQL and RPostgreSQL interaction

[Paul Gilbert]

So it has to do with Sweave. Following Sebastian's model, This vignette 
produces the warning


\documentclass{article}
\usepackage{Sweave}
\begin{document}
\begin{Scode}
library(RMySQL)
library(RPostgreSQL)
\end{Scode}
\end{document}

but running the those lines in an R session does not. I think I will 
re-phrase the issue and move it to R-devel.


Paul


On 12-09-18 02:58 PM, Sebastian P. Luque wrote:

On Tue, 18 Sep 2012 13:46:06 -0400,
Paul Gilbert pgilbert...@gmail.com wrote:


On 12-09-18 01:30 PM, Sebastian P. Luque wrote:

On Tue, 18 Sep 2012 11:40:26 -0400,
Paul Gilbert pgilbert...@gmail.com 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've seen this with a vignette using both the maptools and trip
packages, but it was just a warning and the vignette built just fine.



Yes, it is just a warning, and the vignette builds fine. It also looks
like there is probably a simple fix to remove the problem that causes
the warning, since that is what the warning suggests. However, as
Spencer pointed out, isolating a simple example is not so easy.


I had actually built such an example with those packages (available from
CRAN):

---cut here---start--
\documentclass{article}
\usepackage{Sweave}

\begin{document}

load-packages=
library(maptools)
library(trip)

@

\end{document}
---cut here---end

which produces the warnings:

---cut here---start--
 Warning in .simpleDuplicateClass(def, prev) :
  A specification for class “owin” in package ‘trip’ seems equivalent to 
one from package ‘maptools’ and is not turning on duplicate class definitions 
for this class
 Warning in .simpleDuplicateClass(def, prev) :
  A specification for class “ppp” in package ‘trip’ seems equivalent to one 
from package ‘maptools’ and is not turning on duplicate class definitions for 
this class
 Warning in .simpleDuplicateClass(def, prev) :
  A specification for class “psp” in package ‘trip’ seems equivalent to one 
from package ‘maptools’ and is not turning on duplicate class definitions for 
this class
---cut here---end

Both packages have the same definitions for these classes.  A quick
search on this warning points to
https://stat.ethz.ch/pipermail/r-devel/2011-July/061628.html, which
suggests that adding an importClassesFrom() directive in NAMESPACE and
removing the class definition from one of the packages, might solve
this.  A dependency may be needed though...



___
R-sig-DB mailing list -- R Special Interest Group
R-sig-DB@r-project.org
https://stat.ethz.ch/mailman/listinfo/r-sig-db