Message-ID: <20071219181249.GB31399@eddelbuettel.com>
Date: 2007-12-19T18:12:49Z
From: Dirk Eddelbuettel
Subject: connecting [logging] RMySQL to an external server - SOLVED
In-Reply-To: <200712191951.47805.dusa.adrian@gmail.com>
On Wed, Dec 19, 2007 at 07:51:47PM +0200, Adrian Dusa wrote:
> Hi James,
>
> On Wednesday 19 December 2007, David James wrote:
> > Hi,
> >
> > I'm sorry I'm also coming late to this discussion, but like Dirk, I
> > fail to understand what's wrong with using dbConnect() the way
> > the documentation, (see ?MySQL) suggests.
> >
> > RMySQL was developed in a fully distributed client/server
> > environment, and it uses the MySQL-provided client API. The
> > options that the MySQL client library allows (user, password, host,
> > port or socket file, compression, etc.) should work from RMySQL
> > (RMySQL just passes those directly to the MySQL client library).
> > If you have a specific (e.g., security-related) need that the MySQL client
> > API does not address, then the use of ssh may be the proper way
> > to go. But for simple, vanilla style of client-server communications
> > the underlying MySQL client should be sufficient.
>
> Normally yes, you are right, but this particular MySQL server does not allow
> remote connections (it does not directly listens to port 3306) but only local
> connections using a socket (this terminology is unfamiliar to me, I may talk
> stupid).
> So I have to first create a secure login and only after that connect to the
> remote MySQL server.
Yes, that case is sometimes used on internet-facing or otherwise
widely visible machines where the number of open ports is to be
minimised.
In fact, this may be worth adding as a hint in the DBI or RMySQL
docs...
Dirk
--
Three out of two people have difficulties with fractions.