> >>>> Ordering is slow for large results >> Unfortunately, I use the query for UI related matters that users >> expect to be instantaneous. Currently it can take up to a couple of >> seconds, which users perceive as very slow. > > Usually, the user doesn't expect _large_ results to appear > instantaneous. Instead, GUIs tend to only display one page at a time > (for example, the Google results page).
And that's exactly what I am doing. With h2, even if I want just rows 50000-50050, h2 still has to run the complete query and sort the whole resultset before it returns 50 rows. If h2 was able to use the index, the 50 rows could be returned pretty much instantaneously. Without using an index it takes too long. (unless of course I am doing something else wrong) >> Do you plan to improve h2 to be able to take advantage of the >> existing >> indexes in order to accelerate the described query substantially? > > No, I'm sorry, I don't plan to implement this feature currently. If > you want to do it, please go ahead. If you want to send a patch, > please see http://www.h2database.com/html/build.html#providing_patches I wish I had the database dev skills to do it! Unfortunately that is foreign territory to me. Please don't get my questions the wrong way... h2 is a great database and I am mostly very happy with it and definitely grateful for its existence. You are doing great job, Thomas! -hendrik --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
