>> Ordering is slow for large results, however it doesn't matter how > large the table is. The optimizer doesn't calculate the expected > number of rows at the moment, so it doesn't use the order on the > index. >> Is there any way I can cause H2 to execute this or a similar query >> more quickly? > No, I'm afraid not.
Thanks for your answer, Thomas. 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. Do you plan to improve h2 to be able to take advantage of the existing indexes in order to accelerate the described query substantially? Thanks, -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 -~----------~----~----~----~------~----~------~--~---
