#16906 [Com]: Warning: MySQL: Unable to save result set in ...
| From: | duke at struktuur dot ee | Date: | Mon, 25 Nov 2002 14:41:29 +0000 |
| Subject: | #16906 [Com]: Warning: MySQL: Unable to save result set in ... | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-25788@lists.php.net to get a copy of this message | ||
ID: 16906
Comment by: duke@struktuur.ee
Reported By: vermut@aija.net
Status: Assigned
Bug Type: MySQL related
Operating System: FreeBSD
PHP Version: 4.1.2, 4.2.0
Assigned To: zak
New Comment:
I got the same error message and it disappeared after I did myisamchk
-r /db/mydb/*.MYI
Therefore I doubt that this is a PHP bug at all.
Previous Comments:
------------------------------------------------------------------------
[2002-10-01 04:37:34] g@firebolt.com
I was able to solve this bug by doing the following... granted, the bug
only existed for me once I had a table with > 90000 rows.
Run a:
SET SQL_BIG_TABLES=1;
And MySQL will utilize more memory and be able to save the result set.
Optionally, when done, do this:
SET SQL_BIG_TABLES=0;
(tip courtesy of:
http://www.faqts.com/knowledge_base/view.phtml/aid/9824)
------------------------------------------------------------------------
[2002-09-17 01:38:19] zak@php.net
Assigning all open mysql bugs to myself for 4.3 release.
------------------------------------------------------------------------
[2002-07-23 15:51:18] bugs.php@computer.NOSPAM.creations.nl
I've got the same error on the webserver of my hosting provider (Linux
2.4.13) using PHP 4.2.2 when updating/inserting records to MySQL
(client 3.23.39). Also a simple select of all records (approx. 3750
records, 479Kb in total as line-delimited text)
Anyone got an idea how to solve this?
If you respond, please connect computer and creations in my
emailaddress.
------------------------------------------------------------------------
[2002-07-02 14:53:17] cynic@php.net
umm, I should've added that I've encountered something like this just
yesterday with 4.1.2/1.3.24, 4.2.1/1.3.24 and 4.2.1/1.3.26, but that
was on RH 7.2. and the error mesage was different.
all updates from php were corrupting the tables. updates from mysql(1)
were ok. eventually it got fixed by dumping, dropping, and recreating
the table.
but that's probably completely unrelated.
------------------------------------------------------------------------
[2002-07-02 14:32:40] cynic@php.net
this works with 4.3.0-dev, I'll have to try 4.2.1 tomorrow.
roman@freepuppy ~/install/php4 > cat ./config.nice.cli+apxs
192:0
#! /bin/sh
#
# Created by configure
'./configure' \
'--enable-cli' \
'--enable-inline-optimization' \
'--enable-ftp' \
'--enable-shmop' \
'--enable-sysvsem' \
'--enable-sysvshm' \
'--enable-sockets' \
'--enable-tokenizer' \
'--disable-session' \
'--disable-shared' \
'--with-apxs=/usr/local/sbin/apxs' \
'--with-openssl' \
'--with-zlib' \
'--with-bz2' \
'--with-curl' \
'--with-gettext' \
'--with-iconv' \
'--with-mcrypt=/usr/local' \
'--with-mhash=/usr/local' \
'--with-ncurses' \
'--with-readline' \
'--with-pear' \
'--with-config-file-path=/usr/local/etc' \
'--with-mysql=/usr/local' \
"$@"
<?
mysql_connect('localhost', 'root', '');
mysql_select_db('mysql');
$rs = mysql_query("UPDATE user set user='root' where
user='root'");
if (!$rs)
printf("%d: %s\n\n", mysql_errno(), mysql_error());
else
print("all clear\n\n");
output:
all clear
------------------------------------------------------------------------
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