hard to tell, but I'd guess that our planner is picking a slow plan than sqlite (which is generally a pretty good db)
In this case, it would probably be faster to scan across the main table rather than use a secondary index and then have to access the main table in a random hop.
Particularly if the main table is already sorted by SOME_ID, then the scan can exit early. -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
