Re: [SPAM?]: Re: [PHP-DEV] Make mysqlnd default over libmysql in 5.4
Hi, On 09/07/2011 07:17 AM, Tomas Kuliavas wrote: 2011.09.06 23:20 Ulf Wendel rašė: Am 06.09.2011 21:33, schrieb Stas Malyshev: Hi! Any new PHP major release is about setting new directions. I, Andrey and Johannes, the guys maintaining ext/*mysql* recommend going mysqlnd after an incubation of some four years (5.3x series + dev time). My concern was also that making mysqlnd the default would make libmysql support considered secondary and unimportant. As I was assured it is not the case and the differences between mysqlnd and libmysql flavors seem to be rectified or in the process of being rectified, and I heard no objections for this as a default, I'm OK with it now. Jippie! Removing libmysql support would be crazy. Not only from a PHP perspective but also from a MySQL one. For PHP it is a must-have fallback option. For MySQL the PHP stuff is a nice libmysql test drive. Not a welcome job among the mysqlnd fan boys, as you noticed. But then, sometimes we count mysqlnd vs. libmysql issues... Bouncing bug reports (https://bugs.php.net/bug.php?id=55001) that are not reproducible on setup with mysqlnd when user reports about issue with libmysql is not the way bugs are solved. mysqlnd is not authoritative source for mysql extension behavior. libmysql is. That bug report shows semantics differences Stas was talking about and bug status shows the way you are handling it. If libmysql semantics change between versions, indicate that in bug report instead refusing to solve the problem with 'mysqlnd works fine' The specific case you are talking about is a bug in libmysql. Seems like a very old one as it has been reproduced with a vast range of versions. What Ulf tells you is that you might want to consider mysqlnd, as it had exposed less bugs than libmysql did so far and crashes less in some weirdo cases, than libmysql does. And we talk about libmysql, not the extensions than wrap it. The interface to libmysql won't die, we will support it but be sure that mysqlnd will be better because it is and will be engineered towards the needs of PHP and not like libmysql towards the needs of everyone but the aliens. I hope that even the hardcore supporters for mysqlX@libmysql will some day realize that waiting for a libmysql fix in a mission critical environment will cost them (in time and hence money) a lot more than waiting for the proper mysqlnd fix (applying a patch from svn). Best, Andrey -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [SPAM?]: Re: [PHP-DEV] Make mysqlnd default over libmysql in 5.4
Am 06.09.2011 21:33, schrieb Stas Malyshev: Hi! Any new PHP major release is about setting new directions. I, Andrey and Johannes, the guys maintaining ext/*mysql* recommend going mysqlnd after an incubation of some four years (5.3x series + dev time). My concern was also that making mysqlnd the default would make libmysql support considered secondary and unimportant. As I was assured it is not the case and the differences between mysqlnd and libmysql flavors seem to be rectified or in the process of being rectified, and I heard no objections for this as a default, I'm OK with it now. Jippie! Removing libmysql support would be crazy. Not only from a PHP perspective but also from a MySQL one. For PHP it is a must-have fallback option. For MySQL the PHP stuff is a nice libmysql test drive. Not a welcome job among the mysqlnd fan boys, as you noticed. But then, sometimes we count mysqlnd vs. libmysql issues... Ulf -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [SPAM?]: Re: [PHP-DEV] Make mysqlnd default over libmysql in 5.4
2011.09.06 23:20 Ulf Wendel rašė: Am 06.09.2011 21:33, schrieb Stas Malyshev: Hi! Any new PHP major release is about setting new directions. I, Andrey and Johannes, the guys maintaining ext/*mysql* recommend going mysqlnd after an incubation of some four years (5.3x series + dev time). My concern was also that making mysqlnd the default would make libmysql support considered secondary and unimportant. As I was assured it is not the case and the differences between mysqlnd and libmysql flavors seem to be rectified or in the process of being rectified, and I heard no objections for this as a default, I'm OK with it now. Jippie! Removing libmysql support would be crazy. Not only from a PHP perspective but also from a MySQL one. For PHP it is a must-have fallback option. For MySQL the PHP stuff is a nice libmysql test drive. Not a welcome job among the mysqlnd fan boys, as you noticed. But then, sometimes we count mysqlnd vs. libmysql issues... Bouncing bug reports (https://bugs.php.net/bug.php?id=55001) that are not reproducible on setup with mysqlnd when user reports about issue with libmysql is not the way bugs are solved. mysqlnd is not authoritative source for mysql extension behavior. libmysql is. That bug report shows semantics differences Stas was talking about and bug status shows the way you are handling it. If libmysql semantics change between versions, indicate that in bug report instead refusing to solve the problem with 'mysqlnd works fine' -- Tomas -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
