ID: 19529 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Bogus +Status: Open Bug Type: MySQL related Operating System: Linux 2.4.18 PHP Version: 4.2.3 New Comment:
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. Previous Comments: ------------------------------------------------------------------------ [2002-09-21 14:49:54] [EMAIL PROTECTED] I don't use the MySQL 4 libs. ------------------------------------------------------------------------ [2002-09-21 01:42:05] [EMAIL PROTECTED] Mysql 4.x is still beta quality. So please stick to the stable releases for now. ------------------------------------------------------------------------ [2002-09-20 15:24:56] [EMAIL PROTECTED] 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. ------------------------------------------------------------------------ [2002-09-20 13:28:52] [EMAIL PROTECTED] There is no easily repeatable test case, as this seems to only happen at high load, and it is intermittent. Randomly, mysql_query will fail (more specificly, mysql_db_query), and the error message is "Commands out of sync". MySQL info on error: http://www.mysql.com/doc/en/Commands_out_of_sync.html Other users have confirmed this back to version 4.2.1. We only use the built-in mysql client lib in PHP. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=19529&edit=1
