Bug #16906 Updated: Warning: MySQL: Unable to save result set in ...

From: Date: Thu, 02 May 2002 17:24:14 +0000
Subject: Bug #16906 Updated: Warning: MySQL: Unable to save result set in ...
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-6764@lists.php.net to get a copy of this message
ID: 16906 Updated by: vermut@aija.net Reported By: vermut@aija.net -Status: Feedback +Status: Open Bug Type: MySQL related Operating System: FreeBSD PHP Version: 4.1.2, 4.2.0 New Comment: As I said - every update query fails. I use this example: <?php define ("DB_HOST","localhost"); define ("DB_LOGIN","root"); define ("DB_PSW","password"); define ("DB_NAME","mysql"); mysql_connect(DB_HOST,DB_LOGIN,DB_PSW); mysql_select_db(DB_NAME); mysql_query("UPDATE user set user='root' where user='root'"); ?> Query, executed directly in mysql, works. Previous Comments: ------------------------------------------------------------------------ [2002-05-02 06:34:30] sniper@php.net Please add SHORT but complete example script to this report which can be used to reproduce this. --Jani ------------------------------------------------------------------------ [2002-05-01 05:31:49] vermut@aija.net The problem is: _every_ UPDATE query executed from PHP reports this warning. Data become updated, but execution stops. The same query executed in plain mysql does the same, but does not report a warning. ------------------------------------------------------------------------ [2002-04-30 20:12:41] msopacua@idg.nl This error occured with me, when synching topics in phpBB admin. But my theory is, that for some MySQL errors, php is unable to get the right error string and defaults to 'unable to get result'. The error does show, when you use the mysql client CLI. Could you test that, by executing the exact query that fails, via the mysql client CLI? ------------------------------------------------------------------------ [2002-04-29 11:35:39] vermut@aija.net mysql> CHECK TABLE wpm_tree_en; +----------------------+-------+----------+----------+ | Table | Op | Msg_type | Msg_text | +----------------------+-------+----------+----------+ | project3.wpm_tree_en | check | status | OK | +----------------------+-------+----------+----------+ 1 row in set (0.03 sec) Everything fine, as i see. I do run phpBB, but i run a completely different and unrelated test script. I've done myisamchk -r on all tables. ------------------------------------------------------------------------ [2002-04-29 11:28:42] msopacua@idg.nl Just for fun: on the query that fails, run a CHECK TABLE on the tables involved. See if you get a 'error 134' from table handler. Are you by any chance running phpBB-1.4.x? I've seen this error 'unable to save result set' a few times, while it is actually the above table handler error in mysql. ------------------------------------------------------------------------ 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/16906 -- Edit this bug report at http://bugs.php.net/?id=16906&edit=1

« previous php.bugs (#6764) next »