Currently, the Query... variables (ie QueryStemming, QueryAutoTruncate, QueryWeightFields, QueryFuzzy, and QueryRemoveStopwords) are defined outside a loop, but they should be defined within the loop. This is because each iteration of the loop can disable these variables, which will keep them disabled for each subsequent iteration (and thus each different index/operand pair).
This is still a thing last time I checked... should fix this one of these days...
David, can you tell if this is still valid and provide a little more information?
(In reply to Katrin Fischer from comment #2) > David, can you tell if this is still valid and provide a little more > information? I haven't looked in a long time, but I'd imagine that it's still valid. I think an example is QueryAutoTruncate. When it's on, all the index/operand pairs should have truncation enabled. However, there are some indexes that don't support truncation, so they'll turn QueryAutoTruncate off. So in theory you could have something like this: Pair0-Truncated, Pair1-Can't truncate disable auto truncation,Pair2-NotTruncated, Pair3-NotTruncated When really it should be like this: Pair0-Truncated, Pair1-Can't truncate, Pair2-Truncated, Pair3-Truncated Apologies if that still sounds too vague.
Pretty sure this is still a problem. One of these days I need to sit down and have a big search review...