Hi All,

Due to environment constraints, I have to be able to connect to the local
mysql port (3306) via the hostname "localhost". However, using "localhost"
makes mysql use sockets. This breaks because I don't have a local mysql
server running, hence no socket. I can't seem to find any information about
stopping mysql from using sockets when connecting via "localhost". Can this
be done?

I have inherited code that uses "localhost" to connect to a local mysql
server in the production environment (in about 45 places). In the
development environment, I have a mysql server on a Win2k machine. Because
the code contains connection strings all over the place, I want to be able
to leave the code as is in the development environment and use ssh to
forward port 3306 on localhost to 3306 on Win2k mysql server. I can
successfully do this if I use "127.0.0.1" but it seems the production
environment only allows connections via "localhost" and this can not be
changed.

Any other way around this without having to change connection strings all
the time?

Please reply to the post in comp.databases.

Thanks,

Steph.

Stephan Carydakis wrote:
I've used this technique and localhost has always worked fine, if it's defined
in the hosts file as it should be.

You are using 'ssh -L 3306:localhost:3306'?

-- Lew

Stephan Carydakis wrote:
Hint: set followups.

-- Lew

Lew wrote:
MySQL checks usernames against the host names from which they log in. Check
how the database user name is defined in MySQL. You might need to explicitly
declare the localhost user base.

-- Lew

"Lew" <lew (AT) nospam (DOT) lewscanon.com> wrote

localhost is defined in the hosts file.

Yes. But the problem is not with SSH. Apparently, MySql automatically uses
sockets on Linux when the client connects using "localhost". This takes port
forwarding out of the equation. So how do I tell th MySql client to not uses
sockets?

Steph.

Stephan Carydakis wrote:
I am having trouble understanding what you just said. Port forwarding is all
about sockets. The forwarded 3306 port is forwarded so that socket connections
on the client machine become socket connections on the host machine. That is
hardly "out of the equation". It /is/ the equation.

-- Lew

"Lew" <lew (AT) nospam (DOT) lewscanon.com> wrote

Unix sockets have no concept of ports. When using "localhost" to connect to
a MySql server on Linux. it automatically uses sockets. You can not use
sockets to connect to a remote server. You can only use sockets to connect
to a local MySql server. See my predicament?

On May 27, 2:00 am, "Stephan Carydakis" <scaryda... (AT) nospam (DOT) gmail.com>
wrote:
Yes, it's a special case; therefore you cannot avoid changing the
connection parameters. The fact that these are duplicated in 45 places
is very poor coding practice, and the most humane solution is to
isolate them in a single function. Do it now and reap the rewards
later. :-)

Stephan Carydakis wrote:
A *MySQL* client on Unix can connect to the `mysqld' server in two
different ways: Unix sockets, which connect through a file in the file
system (default `/tmp/mysqld.sock') or TCP/IP, which connects through a
port number. Unix sockets are faster than TCP/IP but can only be used
when connecting to a server on the same computer. Unix sockets are
used if you don't specify a hostname or if you specify the special
hostname `localhost'.

So... don't use locahost, use the actual hostname for tcp/ip connections.



--


Jerry McBride

Stephan Carydakis wrote:
What confused me is that the term "socket" also applies to IP connections.

If you follow others' advice to use TCP/IP to connect then you'll be able to
use SSH.

--
Lew