PHP computation throws garbage into HTTP Headers

[ppowell]

The following class method inexplicably throws garbage into the HTTP headers producing the infamous "headers already produced by" warning:

	/**
	 * Retrieve resultset as an array of objects set up by mysql_fetch_object() PHP function
	 *
	 * @access public
	 * @return object $result
	 */
	function getResult() {										// OBJECT METHOD
		$runquery = $this->runQuery();
		$count = 0;
		while ($row = mysql_fetch_object($runquery)) {
			$result[$count] = $row;
			$count++;
		}
		return $result;
	}

I did some detective work and found the problem only occurs when you NOT comment either of these two lines:

$result[$count] = $row;
$count++;

How on earth could simple PHP computation cause this to occur? Using PHP 4.3.2

Phil

[paulnaj]

Hi ppowell,

If you look in the error log, you'll probably find a 'Notice:' entry saying that you have used am array ($result) before declaring it. I'm not absolutely 100% sure that the notice will produce the 'header' error, but I think it does 😉

So simply put $result = array(); before the while loop (in the same way that you declared $count = 0).

Paul 🙂

[ppowell]

Sorry that made no difference. I am still getting what appears to be a MySQL-generated "silent warning" that flush() is putting onto the output buffers.

I deduced it down to this: Every single table in the "phil" database throws silent warnings when you select more than the allotment of buffered rows per select query. Any other table in any other database, however, throws no silent warnings. Same box, same PHP, same MySQL.

Phil