Hi Thomas, I get the same results running it as the first query after database is opened in both situations. The only thing that I can think of which differs between how my application executes the query vs. how Console does it is that my application is in Groovy and uses it's Sql library, not JDBC directly. I don't think this should make a difference, and the profiler is reporting that the time really is spent inside the JDBC call, but who knows maybe there's something there.
Bill On Jun 9, 9:44 pm, Thomas Mueller <[email protected]> wrote: > Hi, > > It could be a caching issue. To make sure, could you test again with > the H2 Console, but ensure that the database is closed (no .lock.db > file), then open a connection, and run this query (no other queries > before that)? > > One way to speed up multi-dimensional queries > is:http://h2database.com/html/features.html#multi_dimensional > > 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.
