ID: 31175 User updated by: vortexx at freemail dot hu Reported By: vortexx at freemail dot hu -Status: Open +Status: Closed Bug Type: MySQL related Operating System: Windows 2000 Server, SP4 PHP Version: 5.0.4 New Comment:
I apologise for the last message. Using PHP 5.0.4 and MySQL 4.1.11 the problem described in my original post is in fact gone. Previous Comments: ------------------------------------------------------------------------ [2005-04-19 03:14:10] vortexx at freemail dot hu Hello again, I just downloaded PHP 5.0.4 and MySQL 4.1.11, and the same situation persists as before: In case of any queries that contain a CONCAT of a string and data from any MySQL table field, no results are returned via PHP, and also mysql_error(...) returns no error. ------------------------------------------------------------------------ [2005-03-08 01:00:20] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ [2005-02-28 21:14:11] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php5-latest.tar.gz For Windows: http://snaps.php.net/win32/php5-win32-latest.zip ------------------------------------------------------------------------ [2005-02-02 07:36:36] vortexx at freemail dot hu "a) The table is empty or the where clause didn't match any records " Table was not empty, and there was no WHERE clause. Moreover, the exact same query prodiced the expected results with PHP versions prior to 5.0.3. "b) an error occured, which should be checked by mysql_error() - in your case probably illegal mix of collations." Did test for an error - please see my original bug report: none occurred, at least mysql_error returned none. Also please note: same query (on the exact same database, etc.) works fine with PHP versions prior to 5.0.3 . I suspected perhaps this had something to do with the new php_mysql.dll included with the new (5.0.3+) PHP versions?! Since - ceteris paribus - the anomaly was directly linked to changing PHP versions. Once I changed back to the older version, it all worked fine again. If there is any more info whatsoever that you think might be necessary, please let me know! THANKS!!! ------------------------------------------------------------------------ [2005-02-02 06:48:46] [EMAIL PROTECTED] If mysql_query doesn't return a resultset for a select statement this has 2 reasons: a) The table is empty or the where clause didn't match any records b) an error occured, which should be checked by mysql_error() - in your case probably illegal mix of collations. Can't reproduce your error (tested with PHP 4 + 5, MySQL 4.1.10 and 5.0.3 and different character sets on server and client side). ------------------------------------------------------------------------ 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/31175 -- Edit this bug report at http://bugs.php.net/?id=31175&edit=1
