>From going over http://www.mysql.com/doc/en/MySQL_indexes.html (again) http://www.mysql.com/doc/en/Indexes.html (again)
And doing some experimentation it seems that when I build a compound index (A key spanning multiple column) of column types String, int, int - sorting the result takes a very long time when compared to int, int, String - type keys Even though there are more distinct values of strings then ints: and it would make sense to have String 1st as the leftmost prefix to avoid yet another standalone index (since it's required for lookup) the results where an order of magnitude faster. Has anyone else come across this situation? Does anyone have an explanation from a code point of view why this is the case? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]