-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Matt, et al --
...and then Matt W said... % ... % is. But with VARCHAR, whenever the column is given a longer value than % it had since being OPTIMIZEd, a link will be added to point to the part % of the data file where the row continues. :-( ... % Oh and I don't think *disk* fragmentation is an issue because the table % is always scanned and small enough that it will be cached by the OS. % Thus there should never be any physical disk reads after the first % acesses. I don't see the issue, then... If everything is in RAM then your read speed is the same no matter where the data is, so what does a split matter? In fact, I wonder if you could seelect from your split and fragmented table on disk into a temporary table in ram -- which would, having just been created, be unfragmented. Then even if the split mattered it wouldn't matter, so to speak :-) Could you afford a little bit of extra load time at startup to have your un-split, all-RAM, fast table? HTH & HAND :-D - -- David T-G * There is too much animal courage in (play) [EMAIL PROTECTED] * society and not sufficient moral courage. (work) [EMAIL PROTECTED] -- Mary Baker Eddy, "Science and Health" http://justpickone.org/davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE/pIuTGb7uCXufRwARAg+iAKCDoMFQ03OcvO5M/taUwXeCP2TRFACcCUzj Q79WPbchpVKDMKNqUEIWpxA= =0ZRb -----END PGP SIGNATURE----- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
