I do see that the bug was closed over 2 years ago - I guess then it was a persistent problem, but now it is limited to the configuration of the MySQL Server. As I have found out today, Quadrupling the stock memory limits on the MySQL Server solved the problem...not sure what will happen when the database starts growing but, my query is solid, and I am only returning a few rows at a time, so hopefully over a couple hundred queries wont make this thing die! :)
Matt Babineau Criticalcode w: http://www.criticalcode.com p: 858.733.0160 e: [EMAIL PROTECTED] -----Original Message----- From: Michael Stassen [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 01, 2005 3:55 PM To: Michael Dykman Cc: Matt Babineau; 'MySQL General' Subject: Re: Problem with SELECT SQL_CALC_FOUND_ROWS I'm confused. That bug was closed over 2 years ago. What makes you think it applies here, and why do you say it is still "unresolved"? Michael Michael Dykman wrote: > Matt, > > If you go through the various build options tried in that bug report, > you will see that it is a subtle bug and apparently still unresolved. > I couldn't tell you with any degree of confidence will fix it. The > bug report does show a couple of configure options for PHP which seem > to elimiate it, without shedding much light on the underlaying cause. > > Possible conflict in zlib versions or some other common library > between PHP and MySQL build.. I would closely examine the dependant libraries > via $ ldd... Hard to tell without knowing the OS, the specific > software builds and the various library versions especially any shared > ones.. > > If you have a test system you can use, you might consider > experimentally building both PHP and MySQL from source and explicitly > set them to use the same versions of any shared libraries? Might be a > bit of overkill... > > - michael dykman > > > On Tue, 2005-02-01 at 15:51, Matt Babineau wrote: > >>Weird thing is that I am running PHP 4.3.9....I guess I can upgrade >>and see what happens? >> >> >>Matt Babineau >>Criticalcode >>w: http://www.criticalcode.com >>p: 858.733.0160 >>e: [EMAIL PROTECTED] >> >>-----Original Message----- >>From: Michael Dykman [mailto:[EMAIL PROTECTED] >>Sent: Tuesday, February 01, 2005 12:47 PM >>To: Matt Babineau >>Cc: 'MySQL General' >>Subject: Re: Problem with SELECT SQL_CALC_FOUND_ROWS >> >>Matt, >> >> I suspect your problem is PHP, not MySQL. refer to >> >>http://bugs.php.net/bug.php?id=16906&edit=1 >> >>On Tue, 2005-02-01 at 15:20, Matt Babineau wrote: >> >>>Hi All- >>> >>>I'm running a query that uses SQL_CALC_FOUND_ROWS for my search >>>engine on a real estate site. The problem is that I get an error when >>>I run my >> >>query: >> >>>"Warning mysql_query(): Unable to save result set in /clients/search.php" >>> >>>My Query is: >>> >>>SELECT SQL_CALC_FOUND_ROWS propertyData.*, >>>propertyDataBulk.propertyDesc FROM propertyData LEFT JOIN >>>propertyDataBulk ON propertyData.id = propertyDataBulk.propertyID >>>WHERE state = 'CA' limit 0, 5 >>> >>>Very odd that this happens, I am running MySQL 4.1.9 >>> >>>Thanks, >>> >>>Matt Babineau >>>Criticalcode >>>w: http://www.criticalcode.com >>>p: 858.733.0160 >>>e: [EMAIL PROTECTED] >> >>-- >> - michael dykman >> - [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
