re: h2database 1.4.196 We are noticing that the unique index generated for a unique constraint that includes a foreign keyed column is also being used as the index for that foreign key constraint. Is this expected or should the foreign key get it's own index?
We noticed this because when dropping the unique constraint the auto generated unique index was not being dropped. But, if we first drop the foreign key constraint and then the unique constraint the auto generated unique index is dropped. Thanks. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/835bca7e-1bfd-4e8e-9876-f2f0473dcaf4%40googlegroups.com.
