Incorrect index selection when potential index is compound

2001-08-14 Thread Michael Widenius
Hi! > "Eric" == Eric DeCosta <[EMAIL PROTECTED]> writes: >> Description: Eric> Index analysis and optimization is choosing wrong index when a Eric> table involved in a JOIN is compound. MySQL should still be using Eric> the first part of the GECK_STATE PRIMARY key (geck_id) since it is t

Incorrect index selection when potential index is compound

2001-08-13 Thread Eric DeCosta
-+ >Fix: Temporary work-around is not to use a compound index and/or create additional, separate indexes. I suppose throwing the "safe" switch on mysqld would also work. >Submitter-Id: michael6218 >Originator: >Organization: The MathWorks, I