Requesting two rows of data generates almost 100 extra queries?

Looking at the query log dosent seem right, or am I missing something?

When I execute this code:

		$md_sql = "select * from m_data where md_ID = " . $master_ID;

		$movie_data = $db->Execute($md_sql);

		if ($movie_data->RecordCount() > 0)
			{
			while (!$movie_data->EOF)
				{
				echo '<p>Title: ' . $movie_data->fields['md_title'] . '</p>';
				$movie_data->MoveNext();
 		 		}
			}

it returns two records from a table that has only 7 records in it, yet the #of queries reported jumps from 336 to 423

Does it really take 87 queries to select two records out of seven? Or is the way the queries are counted wrong? Or am I doing something wrong?

Yes, the table is properly indexed.

If it's true, is there any way to make this more reasonable?

I think you're doing something wrong with how you're structuring the use of your custom code ... perhaps you've got your query stuck in the middle of a loop, thus causing it to run multiple times.

Well, if it was looping and executing more than once, the test-echo stmnt would fire in each iteration through the loop and make the problem obvious.

Its copied almost verbatim from the example in the wiki with the exception of the table/field names.

The snippit in question executes in includes/modules/pages/product_info/main_template_vars.php to pull in some data from an additional table in the ZC database.

It runs immediately after the main select at about line 46-ish

If it matters, it does return the expected data. The echo stmnt is just for testing.

The results have me worried as this table will eventually contain ~100,000 rows.

Would it be more efficient to just use $result=mysql_query(...)?

Thanks for your expert eye.

The code you posted is just one single query. Unless you've done other changes which you've not mentioned.

Anything else that's changing must be related to other things happening on the page ... perhaps you have a New Products box enabled, and certain products are on sale but others aren't, and when the ones on-sale appear they require additional queries to calculate/display appropriate details, etc.