On Friday 28 March 2003 04:39, harlan at artselect dot com wrote: > When querying a largish (370,000 rows) table, a unique compound index > on its three int columns performs slower (as slow as no index at all) > than when I use the same index created without the "unique" keyword. > > I've repeated it dozens of times: Create the index unique, and it's > slow, create it non-unique and it's fast. The EXPLAINs look the same > for both. > > Is this to be expected under some circumstances, or do I get to > isolate this messy situation (it's an ugly query) for a bug report?
Please show your table structure, your query and the result of EXPLAIN of that query - then we'll help. For now, the information provided is not enough to make a decision. > --Pete -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
