Thijs Kinkhorst schrieb:
On Tue, March 4, 2008 12:35, Sebastian Mendel wrote:
especially on shared hosters, where the most 'bad' database structure will exist, this could have very heavy impact on performance of the MySQL server, or?
I'm not backed by any facts. but my common sense says that parsing a many-kB long request uri should at the very least be comparable to calculating an md5 sum.
parsing ONE "many-kB long request uri"
vs.
calculating MD5 for EVERY row in the table ... (or at least till the offending was found)
and what about normal tables with many fields or large text fields (when inserting or editing)?
Note also that on the total use of the database, editing or deleting these rows are relatively rare operations.
"these rows"? why do you think someone will edit or delete "these rows" less than any other row?