Hi all, All in all I'm really happy with H2 and (almost) everything works as it should.
While looking at a query, with bad performance I came upon strange behaviour, though: H2 didn't use the primary key index to do a join which had only the table's primary key in the on-clause (explain showed a scanCount for that join of 106757553). After dropping the Index and recreating the primary key, the index was used (the scanCount was down to 35003). The only difference in the index before and after the recreation is, that the one before had IS_GENERATED = true and the one after had IS_GENERATED = false. It seems as if the index was there and if I understand the explain syntax correctly the optimiser decided to use it, but then scanned the whole table anyways in spite of the existing Index. Has somebody come across such a behaviour before? -- 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.
