If I understand correctly, H2 doesn't allow indexes on CLOB or BLOB columns.
If I still understand correctly, column selectivity is used solely to calculate which index to use. The auto-analyze that H2 performs calculates the selectivity for CLOB and BLOB columns. This seems of no use. It seems to me that it can also cause a large H2 database to pause for a significant amount of time, causing unnecessary memory churn. I've tested out this theory and concluded that auto-analyze is 10 to 20 times faster when running on a simple table containing two INT column and one CLOB field. Is this optimisation worth implementing? -- 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.
