As far as I am aware, the problem with the query optimizer is that it does not use indexs in every situation that one might expect. But yours seems to be using the index. So, I don't know what else it could be (but I am no expert at H2).
How long does it take to run the query? How many rows are there, and what is the general size of the rows (number of columns)? On Thursday, January 19, 2017 at 5:47:55 AM UTC-5, Anil Dasari wrote: > > Hi Adam, > > I mean query is very slow. Explain plan looks good and it is using index. > I did not compare with other databases. > > Thanks. > -- 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 h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
