Hi I'm having a hard time understanding the output of EXPLAIN ANALYZE for a SELECT statement. I'd appreciate some explanation in the documentation. Specifically: - What exactly does the scanCount stand for? As far as I understand, it is not the size of the current result set. Is it the number of index / table look-ups? - All join conditions are replaced by "ON 1=1", the actual conditions have been moved to the WHERE part. What does this tell me? I don't assume H2 actually performs the cartesian product first for all joins.
I'm working on a performance problem where an additional restriction in the WHERE part results in a 12 times slower execution which I just cannot explain. I'll be glad to post the query if someone is interested. I'm working with v1.2.139. Regards, Remo -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
