Is there an solution for the behavior of mysql, described below?
I'm using mysql 3.23.41 on MacOSX...
The problem is, that MySQL isn't able to use indexes for OR in the WHERE
clause yet and therefore the additional OR prevents optimal use of
indexes. MySQL uses only one index for a select, so it
Michael Braun wrote:
I'm using mysql 3.23.41 on MacOSX...
The problem is, that MySQL isn't able to use indexes for OR in the WHERE
clause yet and therefore the additional OR prevents optimal use of
indexes. MySQL uses only one index for a select, so it can't use an index
when there is an