Noel Grandin wrote > Fixed in SVN. > > Looks like I introduced the bug when I did the ConditionInConstantSet > performance thing.
Many thanks for your fast fix: however I noticed the SELECT COUNT that uses the OR condition now give wrong result (0 rows)... do you confirm it? Please try the following test case. It's a corrected version of the original one, where accidentally the two queries previously differ in the where condition semantic (OR param values) -- View this message in context: http://h2-database.66688.n3.nabble.com/huge-performance-difference-between-SELECT-WHERE-x-IN-1-2-and-SELECT-WHERE-x-1-OR-x-2-tp4026210p4026256.html Sent from the H2 Database mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
