I noticed there are a lot of cases where h2 doesn't use indexes very well.
On small tables it doesn't make much of a difference. The bad index use is very noticeable on large tables. Brish On Sep 2, 8:34 am, "Thomas Mueller" <[EMAIL PROTECTED]> wrote: > Hi, > > >> C. SELECT pk FROM t WHERE pk = ? OR pk = ? [7688ms] > > Nearly 8 seconds, is that right? > > Yes. This statement is not optimized at all, a table table scan is > made. It is planned to improve that, see "Optimize ID=? OR ID=?: > convert to IN(...)" on the roadmap. However the priority of this item > is not very high currently. > > Regards, > Thomas --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
