Hi,
There are 2 tablescans in the query, there should only be one. > Thomas and Noel correct me if I'm wrong, but H2 treats each Select statement separately in a depth-first-search fashion. According to the optimization strategy, the first table of the sequence always get a table Scan, because there's no evaluable condition index. Can you elaborate more why you think the should only be one tableScan? Regards, Fred -- 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. For more options, visit https://groups.google.com/d/optout.
