Edit report at http://bugs.php.net/bug.php?id=48082&edit=1
ID: 48082 Comment by: peaceable_whale at hotmail dot com Reported by: andrew dot answer at gmail dot com Summary: mysql_connect does not work with named pipes 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: I do not agree that supporting named pipe is a new feature. Named pipe allows MySQL Server in Windows to operate without TCP/IP and the MySQL Client Library has been supporting it. mysqlnd should have been able to connect MySQL Server via named pipe since its intrduction. The patch just added the missing feature back. Since there is no timeframe for the next minor PHP version, it is quite unfair to ask those relying on named pipe to wait for that. Please add support to named pipe in 5.3.x. Previous Comments: ------------------------------------------------------------------------ [2010-09-22 17:16:39] and...@php.net 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. ------------------------------------------------------------------------ [2010-09-22 17:14:05] and...@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] and...@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. ------------------------------------------------------------------------ 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
