On 2009-12-03 16.05, Niclas Hedhman wrote:
On Thu, Dec 3, 2009 at 1:27 PM, Rickard Öberg<[email protected]> wrote:
The rule I use is: if an = is not used within an "or"-statement, then it's
ok to inline the value comparison. If there's an "or" going on then I think
the FILTER still has to be used, to get correct semantics.
Any OR at all, or just those that matter?
I skipped all OR's, because I couldn't see how to make it work with
inlined values and OR.
I think the optimizations possible are; If you have a Syntax Tree,
then all top level expressions that are ANDed and have a Literal 2nd
operand can be moved outside the FILTER clause.
That's pretty much what I concluded as well.
But perhaps this (whatever "this" is) is good enough for now, as there
are many other important things to deal with.
Yes. But, for us the whole thing became unusable without it, as we had
queries taking many minutes before this fix. Without it we'd have to do
progress bars and whatnot, and now we can just let the user wait a
couple of seconds instead, which is better.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
