So if we already have hash indexes, does H2's planner currently skip using the selectivity system (and periodic scanning N rows)?
It seems like this could produce better results, given the scenario where the first N rows for a column might have duplicates and appear to have lower selectivity, when the entire column's actual uniqueness might be much higher than others, in the context of millions of rows. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/smGZ2EyOW7AJ. 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.
