#48082 [Com]: mysql_connect does not work with named pipes
| From: | quakvorgus at yahoo dot com | Date: | Wed, 17 Feb 2010 20:11:17 +0000 |
| Subject: | #48082 [Com]: mysql_connect does not work with named pipes | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-147799@lists.php.net to get a copy of this message | ||
ID: 48082
Comment by: quakvorgus at yahoo dot com
Reported By: andrew dot answer at gmail dot com
Status: Assigned
Bug Type: MySQL related
Operating System: win32 only - Windows XP
PHP Version: 5.3.0RC1
Assigned To: mysql
New Comment:
Confirming what andrew wrote.
@kulakov74: Thanks for the information. Setting mysql.default_socket =
mysql does not solve the issue for me.
Will have to switch to tcp connections instead of using named pipes.
Please, the official documentation should be updated about this change
from php 5.2 to 5.3.
Previous Comments:
------------------------------------------------------------------------
[2010-02-02 07:07:14] peaceable_whale at hotmail dot com
I have the same problem using PHP 5.3.1 on IIS 7.5 w/FastCGI and MySQL
5.1.43. Is there any update on this issue?
------------------------------------------------------------------------
[2009-10-20 19:56:25] kulakov74 at yandex dot ru
I confirm this with the just installed PHP 5.3.0 on Win XP, I used to
use pipes and had skip-networking in my my.ini, I still can connect with
mysql.exe, but PHP does not connect this way any more - I had to comment
out skip-networking and set the right port in mysql.default_port = 3306
(PHP used to work without it when I used TCP long ago).
Yes, the dot does not work any more, as if it cannot be resolved to
localhost.
If I have mysql.default_socket = mysql in my php.ini, mysqlnd connects
to localhost via UNIX socket, otherwise it uses TCP.
I agree these things are not critical, yet they have to be mentioned or
explained somewhere.
Got some info on pipes here: http://blog.ulf-wendel.de/?p=157
(comments)
------------------------------------------------------------------------
[2009-06-29 09:43:02] andrew dot answer at gmail dot com
http://stackoverflow.com/questions/832714/mysql-named-pipes-on-windows-
faster-best-practice-or-bad-idea
------------------------------------------------------------------------
[2009-06-29 09:40:48] andrew dot answer at gmail dot com
regarding performance
http://www.google.ru/search?
rlz=1C1GGLS_ruRU305RU305&sourceid=chrome&ie=UTF-8&q=named+pipes+speed
http://www.mail-archive.com/mysql@lists.mysql.com/msg77837.html
http://msdn.microsoft.com/en-us/library/aa178138(SQL.80).aspx
------------------------------------------------------------------------
[2009-06-29 08:42:28] uwendel at mysql dot com
Aren't named pipes considerable slower than TCP/IP: why use named pipes
?! I won't work on named pipe support for mysqlnd, if its slower, which
is the case AFAIK.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/48082
--
Edit this bug report at http://bugs.php.net/?id=48082&edit=1