On 2013-07-12 09:03, Lukas Eder wrote:
In exceptional cases, OFFSET clauses can be most efficiently
implemented by counting and skipping the largest possible logical data
sets in either a TABLE or INDEX structure, according to the specified
SELECT query.
It should be possible to pass this information down to our Index classes
and have them perform the skipping.
The downside is that this optimisation is only applicable to top-level,
single-table queries.
Anything else would have to fall back to the current implementation.
Given that the OP was asking about a synthetic benchmark, not a
real-world use-case, I agree that it is not worth the extra complexity.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.
