My company, Guidewire, is attempting to move from H2 1.2 to 1.4 to take advantage of the MVStore feature that should greatly reduce deadlocks.
Is it possible to change the behavior of H2 1.4 so that when a FK constraint is created it will not also create a single column index on that column if a multicolumn index already exists with that column as a leading key? in our case, many of our tables have a RETIRED column that is non-zero for rows that have been logically deleted. For columns being turned into a FK, there is already a two column index on the FK column and RETIRED, so we don't need and or want or expect a separate single column index on that FK. The behavior seems to have changed since 1.3. -- 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/d/optout.
