RE: Problem with SELECT SQL_CALC_FOUND_ROWS

Ok I installed PHP 4.3.10 and it still has not fixed the problem. If I remove the SQL_CALC_FOUND_ROWS from the query, it works no problems! This is very strange behavior! Matt Babineau Criticalcode w: http://www.criticalcode.com p: 858.733.0160 e: matt@criticalcode.com -----Original Message----- From: Matt Babineau [mailto:matt@criticalcode.com] Sent: Tuesday, February 01, 2005 12:52 PM To: 'Michael Dykman' Cc: 'MySQL General' Subject: RE: Problem with SELECT SQL_CALC_FOUND_ROWS 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: matt@criticalcode.com -----Original Message----- From: Michael Dykman [mailto:michael@dykman.org] 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: matt@criticalcode.com -- - michael dykman - michael@dykman.org -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=matt@criticalcode.com