> I'm wondering whether this has something to do with the following words of > wisdom in the reference manual: > "For tables that changes a lot you should try to avoid all VARCHAR or BLOB > columns. You will get dynamic row length as soon as you are using a single > VARCHAR or BLOB columns." > > but I don't see why this should matter. Why does it matter that > row lengths > are dynamic ? Surely the index doesn't just specify a row "index" that is > multiplied by the row length ? Surely it contains some sort of row data > offset to allow for variable row lengths. > >
I've seen it happen -- we had a table that was taking 2-3 seconds for a keyed lookup, and it should have been in the miniscule range. We OPTIMIZEd the table, and after that the queries in question executed in 0.1 or 0.2 sec. However, this was after several months of abuse -- it shouldn't be the case on a newly created table. Steve Meyers --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
