php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #4759 MySQL: Unable to save result set
Submitted: 2000-06-01 18:14 UTC Modified: 2000-06-11 03:48 UTC
From: cnewbill at onewest dot net Assigned:
Status: Closed Package: MySQL related
PHP Version: 4.0.0 Release OS: Redhat Linux 6.2
Private report: No CVE-ID: None
View Add Comment Developer Edit
 [2000-06-01 18:14 UTC] cnewbill at onewest dot net 
ANY script that uses mysql(),mysql_db_query, and mysql_query() produces warnings as follows.

MySQL: Unable to save result set in SCRIPT on line XXX

In previous compile jobs this did not happen and just started happening out-of-the-blue this morning.

Using PHP 4.0.0 as a DSO.  MySQL version 3.22.10.  

NOTE: Exact same query causes no problems or warnings when run from the mysql command line.

I see that I am not the only one with this strange problem.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2000-06-01 18:51 UTC] cnewbill at onewest dot net 
Forgot two important details, the query still executes properly and it does not happen when doing a SELECT statement only when using UPDATE and DELETE and probably anything else that doesn't actually return a result set.
 [2000-06-03 07:54 UTC] cnewbill at onewest dot net 
Okay here is the skinny on what I found out.  First, when configuring your build for PHP4 you MUST specify a MySQL directory.  This is where the problem is generated.  If you do not the configure script assumes that it can use its libmysql, which is included with the PHP4 source in ext/mysql/libmysql.  The version of MySQL it is using is 3.23.10-alpha which is NOT the version I am running.  There-in lies the goof up.
 [2000-06-03 20:06 UTC] rasmus at cvs dot php dot net 
This bundled libmysql code should be completely backward compatible
with older versions of MySQL.  If you have found a compatibility issue,
please report it to the MySQL folks.
 [2000-06-10 18:52 UTC] zeev at cvs dot php dot net 
The solution you found is most probably accurate;  The reason for it is not that PHP's MySQL support is incompatible with your server, but that you most probably have at least one other Apache module that uses MySQL (e.g., mod_auth_mysql or PHP 3.0), which is linked against the local MySQL client library.  PHP 4.0 being linked to its bundlied MySQL client library in the same process as another module linked with the local MySQL client library would result in various problems, such as this.
 [2000-06-11 03:48 UTC] cnewbill at onewest dot net 
Bingo!

I am using mod_auth_mysql as well.  I didn't think that the folks over at MySQL qould have a blunder like that, we have used MySQL for long time and are very pleased with it and PHP.  Keep up the good work.
 [2003-02-23 08:46 UTC] no at email dot com 
cnewbill at onewest dot net said

> First, when configuring your build for PHP4 
> you MUST specify a MySQL directory

Would you guys PLEASE be so kind to update the INSTALL file shipped with php to include this information? That would help about 1000 hours of useless bitching.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Thu May 16 14:01:32 2024 UTC