ID:               45468
 Updated by:       [EMAIL PROTECTED]
 Reported By:      michael dot kofler at gmx dot com
-Status:           Open
+Status:           Assigned
 Bug Type:         MySQLi related
 Operating System: *
 PHP Version:      5.3-alpha1
 Assigned To:      uw


Previous Comments:
------------------------------------------------------------------------

[2008-08-07 08:01:44] michael dot kofler at gmx dot com

re-tested on Linux with alpha1, compiled with this configuration:

configure --with-mysqli=mysqlnd \
    --with-mysql=mysqlnd \
    --with-mysql-sock=/var/run/mysqld/mysqld.sock \
    --enable-pdo \
    --with-pdo-mysql=mysqlnd \
    --with-apxs2=/usr/bin/apxs2 \
    --with-zlib \
    --with-gd \
    --with-config-file-scan-dir=/etc/php5/apache2 \
    --with-jpeg-dir=/usr/lib \
    --enable-exif \
    --libdir=/usr/lib \
    --enable-mbstring  

also tried

    --with-mysql-sock=/var/run/mysqld \

result: mysql, mysqli and PDO/mysql, all using mysqlnd, still look for
the socket file /tmp/mysql.sock and ignore --with-mysql-sock

if I compile without mysqlnd and without the --with-mysql-sock option,
PHP automatically finds the right socket file, probably because libmysql
reads the [client] settings in /etc/mysql/my.cnf

my solution for now: I changed all socket options in /etc/mysql/my.cnf
and /etc/mysql/debian.cnf

it would be better either to provide a working configure option for PHP
(--mysqlnd-sock=...) or to evaluate my.cnf within mysqlnd

------

PS: as to mysqlnd not supporting old MySQL authentication: perfectly
fine for me, but *do document* it in some PHP 5.3 update advisory;
otherwise I am pretty sure the update to PHP 5.3 will cause trouble for
many MySQL users

------------------------------------------------------------------------

[2008-07-23 11:37:26] [EMAIL PROTECTED]

>From the begin on mysqlnd has been described as MySQL 4.1+. We won't
make it work with any MySQL <4.1. See also the MySQL Lifecycle Policy.

Those distributions that use old_passwords=1 have two choices: use a
different configure for PHP and use libmysql like ever since or take the
challenge of an upgrade. PHP 4 will become history at some point in time
and so will MySQL 4.1.

If you are using MySQL < 4.1 and it works with libmysql all is fine.
mysqlnd is does not support MySQL <4.1 nor does it support
old_passwords=1: no bug.

------------------------------------------------------------------------

[2008-07-21 18:23:31] [EMAIL PROTECTED]

The old authentication method is insecure and should not be used. Also
MySQL servers before 4.1 are already antique. If you have an application
that uses them you might don't want to change you PHP, and you still
have the possibility to compile PHP with libmysql. mysqlnd will never
support the old authentication. This saves hassles when checking what is
possible and what not. 4.0 and earlier are too old.
I just committed a fix, so it will be possible to configure PHP with
--with-mysql-sock to use another socket. However, the problem _wasn't_
in mysqlnd but in the extensions that sit on it. If you use libmysql it
will look by default for a socket under /tmp/mysql.sock . That's the
default. During server compilation you can set different default value
which will appear then in mysql_version.h that comes with libmysql and
what is used by the binary. mysqlnd uses /tmp/mysql.sock and there is no
way to change it on it's level, but with the existing option it will be
on the extension level.

------------------------------------------------------------------------

[2008-07-15 07:36:41] michael dot kofler at gmx dot com

Linux: you were right, it's a socket problem

--with-mysqli=mysqlnd looks for the socket file at /tmp/mysql.sock

is there a ./configure option or another way to set the default socket
file? I set a link from /tmp/mysql.sock to /var/run/mysqld/mysqld.sock,
but that's a hack and no solution

Windows: no error message is shown; the browser waits for ever for an
answer but does not get one; the Apache log file also shows no errors

PS: if mysqlnd is to be used by default in PHP 5.3, it really should be
*completely* backward compatible (as advertised); right now, this is not
the case; while the socket file problem can probably fixed with the
right configuration, mysqlnd apparently requires the new MySQL
authentication (introduced in MySQL 4.1); some Linux distributions still
ship my.conf with old_passwords=1 to get maximum compatibility to old
client libraries (I know, that's a bad idea ...); for this reason, PHP
5.3 will not work out of the box in many, many cases ...

PPS: I am now offline till July 22nd, so I can give no more feedback
till then

------------------------------------------------------------------------

[2008-07-14 18:27:56] [EMAIL PROTECTED]

... make use of the functions and report back what error you get.

------------------------------------------------------------------------

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/45468

-- 
Edit this bug report at http://bugs.php.net/?id=45468&edit=1

Reply via email to