Steven Roussey wrote:
>> "ORing on two different fields" is what I have been asking about :).
> This is not optimized, and I don't think it is set to be optimized
> until 5.1 (as per someone else's comment).
>> Using a composite index was suggested
> This is bad information. It works for AND, not for OR.
> You have two workarounds: temp tables and unions.
By a twitch of algabra, how about ...
"select * from sometable where not( f1 != 123 and f2 != 123 )",
... at least it gives an AND to optimize.
Then again, I maight be too optimistic.
HansH
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
