Hi David,
I do not have email access so I give you the evidence they sent me.
{email saved}
They say that this use damages the use of the server also for other clients. Where ist there an abuse? This is a normal use of MSQL. Please look into it.
Regards
Roland
Hi David,
I will run the test asap. What is what you called slow query log trigger? And what do the figures belonging to the "TIME" coloumn express?
Would you please help me to understand the logs?
Regards
Roland
Hi David,
The following result on running the test is shown:
Array
(
[0] => Array
(
[id] => 1
[select_type] => SIMPLE
[table] => products
[type] => ref
[possible_keys] => name,name_2,namedescription
[key] => name
[key_len] => 257
[ref] => const
[rows] => 1
[Extra] => Using where
)
)
Regards
Roland
Hi Roland,
Thanks - i'll look into this for you.
Cheers,
David.
Hi Roland,
They are normal indexed queries so I'm not sure why they should cause the slow query log trigger. However, I'm wondering if through making any modifications that the indexes have become changed and it is no longer using the correct index for the query.
One way to check this, if you could run the following test script from the main Price Tapestry installation folder and let me know what is displayed....
test.php
<?phpheader("Content-Type: text/plain;");
require("includes/common.php");
$sql = "EXPLAIN SELECT * FROM `".$config_databaseTablePrefix."products` WHERE name='Testing'";
database_querySelect($sql,$result);
print_r($result);
?>
Cheers,
David.