#19529 [Com]: Occational "Commands out of sync" errors

ID: 19529 Comment by: joc@presence-pc.com Reported By: sroussey@network54.com Status: Bogus Bug Type: MySQL related Operating System: Linux 2.4.18 PHP Version: 4.2.3 New Comment: I agree MySQL 4.x is still in beta quality (although it works quite well), but before upgrading to php 4.2.1 I had strictly no problem with PHP / MySQL 4.x (and I'm using MySQL 4.x libs). Previous Comments: ------------------------------------------------------------------------ [2002-09-21 15:17:40] sander@php.net IMHO, it's not a good idea to use MySQL 4.x. It's certainly not a good idea to use 3.x libs to access a 4.x server. ------------------------------------------------------------------------ [2002-09-21 15:14:58] sroussey@network54.com Additional information: this issue seems to only happen when using mysql_pconnect. I switched to mysql_connect and the issue has gone away. Seems to be an issue with persistent connections. ------------------------------------------------------------------------ [2002-09-21 14:49:54] sroussey@network54.com I don't use the MySQL 4 libs. ------------------------------------------------------------------------ [2002-09-21 01:42:05] sniper@php.net Mysql 4.x is still beta quality. So please stick to the stable releases for now. ------------------------------------------------------------------------ [2002-09-20 15:24:56] joc@presence-pc.com Same problem for me with PHP 4.2.1 and MySQL 4.0.x. mysql_query sometimes fails just after calling mysql_select_db (I'm not using mysql_db_query). (only under high query per second). Sometimes I'm not experiencing the error message but mysql_query fails to return a valid resource identifier (and then mysql_fetch_row fails) - again first mysql_query after mysql_select_db is affected -. I'm using pconnect with mysql. I'm linking statically with the mysql lib provided with mysql 4.0.x. ------------------------------------------------------------------------ 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/19529 -- Edit this bug report at http://bugs.php.net/?id=19529&edit=1