#520 connect via named pipe

[Anonymous]

Originally created by: a...@anse.de
Originally owned by: a...@anse.de

Requested as enhancement #1911564 by nobody@sf on 2008-03-10 18:33

Hi,

On my windows XP system I have disabled ip access to MySQL due to security
concerns. It would be great if
HeidiSQL could connect to MySQL via a named pipe.

[Anonymous]

Originally posted by: a...@anse.de

(No comment was entered for this change.)

Labels: -migrated

[Anonymous]

Originally posted by: gabylas... (code.google.com)@gmail.com

Hello,

I run several MySQL Servers using named pipes and also would like to be able to
connect to HeidiSQL to those servers. I'm actually only able to connect to only one
server at a time.

Actually it's only possible to connect to one server at a time if the socket name is
"mysql" and using "." as host name. It is possible to connect to other servers with
different socket name by setting the environment variable "MYSQL_UNIX_PORT" to that
socket name (example : mysql.sock). However this will prevent you to connect to
other servers, including the one with socket name = "mysql"...

The solution is simple. Allow people to type the socket name instead of the port
number, only if the host is ".". Doing like that will allow people to add several
connections using named pipes with different socket names.

Regards,

Gabriel Hautclocq

[Anonymous]

Originally posted by: gabylas... (code.google.com)@gmail.com

Hello,

I created a patch who add support for named pipe connections. You can now have
several MySQL servers running in your machines using named pipes and manage all of
them with HeidiSQL.

Beware of possible bugs because first I am not a Delphi developper (first time
today), I had to change the format of connection string in the zeosdbo package to
support unix sockets, and it's possible that I forgotten to modify some parts of the
code. However it seems to actually work very well for now.

Also attached the resulting executable so you can try it, and a screenshot of the
new connection window with a socket name field.

Regards,

Gabriel Hautclocq

[Anonymous]

Originally posted by: a...@anse.de

Awesome, thanks a lot man! Added you to our contributors here at Google Code.

I just reviewed your patch and think we should integrate it (however, leaving out
some irrelevant changes in the patch but that's minor).

How do I have to configure my local MySQL server on Windows to accept named pipes
connections?

[Anonymous]

Originally posted by: gabylas... (code.google.com)@gmail.com

Hello,

I'm glad that you like it! However please could you check that I don't break
something before you integrate the patch ? Because I'm very new to Delphi...

Well, here is what you should have at least in your my.ini to use named pipes :

[client]
#port is optional in named pipe mode,
#but you still can configure a different port for each server.
port=3308
pipe

socket=mysql.sock
# (or whatever you want as socket name)

[mysql]
#some params...

[mysqld]
port=3308
skip-networking
enable-named-pipe

# The Pipe the MySQL Server will use
socket=mysql.sock

====================

That's all you need to use named pipes. Then start your server with those params.

[Anonymous]

Originally posted by: gabylas... (code.google.com)@gmail.com

In HeidiSQL, don't forget to put "." without the quotes as host, don't use
"localhost", or it will not work.

[Anonymous]

Originally posted by: a...@anse.de

This issue was closed by revision [r2554].

Status: Fixed