Thanks, but that's pretty much what we'd expect, but it doesn't tell us
anything new.
Adding an index on nanoTime is of course going to make the query run faster.
The interesting question is: Why is the query so much slower on H2 than
on Derby when there is no index.
The most likely reason is that you created an index on Derby, and then
forgot about it.
So we need some kind of proof that H2 is doing something silly compared
to Derby, which is why I need you to do an EXPLAIN PLAN on your Derby query.
On 2012-07-12 08:43, Bartosz Skorupa wrote:
I made some tests with my DB and I have some interesing observation ->
look attachment.
Pozdrawiam
Bartosz Skorupa
--
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.
