Thanks for the info! I was able to fix it quickly by adding a migration to rename the constraints and adding a baseline so the individual migrations are skipped for my tests.
On Wednesday, April 9, 2025 at 6:33:05 a.m. UTC-4 Evgenij Ryazanov wrote: > Hello! > > In the SQL Standard names of constraints must be unique within a schema > and H2 is implemented in that way. Some data definition commands from the > Standard and INFORMATION_SCHEMA depend on this uniqueness. So no, it isn't > possible and it shouldn't be possible to have such configuration option, it > is too complex by itself and it will break some important features, such as > possibility to read database metadata. -- 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 visit https://groups.google.com/d/msgid/h2-database/febf8e2e-6081-48e2-8c9d-1ff39ff271f6n%40googlegroups.com.
