Ah, I see.
I know I *can* specify the socket at runtime in DBD::mysql, but I am using a whole load of
someone else code, which doesn't specify the mysql socket.... so unless I can get
DBD::mysql to work with the socket default, i will have to do 1000s of find ->
replaces to add the extra parameter to the calls to DBI->connect(). And then each
time the software is updated, do it again.
So what you seem to be saying is that I need to re-install mysql or do the above?
-----Original Message-----
From: Jochen Wiedmann [mailto:joe@stripped]
Sent: 15 September 2003 14:18
To: michael watson (IAH-C)
Cc: 'perl@stripped'
Subject: Re: FW: Problems with mysql.sock
michael watson (IAH-C) wrote:
> My real problem is with DBI::mysql
This is exactly what I was talking about. :-)
> It's almost as if I have two versions of mysql on my machine, but I don't.
You have. :-) The location of the MySQL socket is compiled into the server,
into the client library (for example libmysqlclient.a) and into the client
binaries (for example "mysqladmin" or "mysql"). Each of them *may* have a
different location, which seems to be the case on your system.
Jochen
