plan difference was intentional.
Thanks for taking a look at this,
—Chris
On Jan 15, 2014, at 11:14 PM, Richard Hipp wrote:
> On Wed, Jan 15, 2014 at 6:13 PM, Chris Swinefurth wrote:
>
>> The query:
>> SELECT terms.term, terms.id, terms.type, terms.produ
Guys,
I’ve identified a detrimental query planner change between 3.7.12 and
3.8.1. It appears to be a change from the 3.8 NGQP. A query with a like where
clause with “collate nocase” now uses a full table scan instead of a covering
index. This occurs even if the case_sensitive_like pr
2 matches
Mail list logo