Edit report at http://bugs.php.net/bug.php?id=48082&edit=1
ID: 48082
Updated by: andrey@php.net
Reported by: andrew dot answer at gmail dot com
Summary: mysql_connect does not work with named pipes
-Status: Analyzed
+Status: Closed
Type: Feature/Change Request
Package: MySQL related
Operating System: win32 only - Windows XP
PHP Version: 5.3.0RC1
Assigned To: mysql
Block user comment: N
New Comment:
Support will be in the next minor PHP version, be it 5.4 or something
else. 5.3.x won't get this, as this is classified as new feature.
Previous Comments:
------------------------------------------------------------------------
[2010-09-22 17:14:05] andrey@php.net
Automatic comment from SVN on behalf of andrey
Revision: http://svn.php.net/viewvc/?view=revision&revision=303679
Log: Fix for
Request #48082 mysql_connect does not work with named pipes
------------------------------------------------------------------------
[2010-08-20 12:24:54] andrey@php.net
A patch is being worked on
------------------------------------------------------------------------
[2010-05-18 20:31:05] dex_is_cool at loopmod dot com
I can't get named pipes working.
It _always_ falls back to TCP, and fails if it can't get TCP
connection.
Windows XP sp3
IIS 5.1
FastCGI
php-5.3.2-nts-Win32-VC9-x86
------------------------------------------------------------------------
[2010-02-17 20:11:16] quakvorgus at yahoo dot com
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.
------------------------------------------------------------------------
[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?
------------------------------------------------------------------------
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/bug.php?id=48082--
Edit this bug report at http://bugs.php.net/bug.php?id=48082&edit=1