|
As far as dropping, I do not see anywhere in 4.x that explicitly drops the unique keys. Well, I do see it used from SchemaUpdate in 4.x, but I mean from SchemaExport I do not. So where are you seeing this call happening from?
As far as dropping, that looks like a call I missed in moving to the concept of an Exporter. So the StandardTableExporter does not have a call to UniqueDelegate#getTableCreationUniqueConstraintsFragment as it problem should. So please try this as confirmation.. well one of 2 things...
-
Have your MyHSQLDialect (from the test) return a copy of StandardTableExporter that adds the line buf.append( dialect.getUniqueDelegate().getTableCreationUniqueConstraintsFragment( table ) ); just after the point where it adds the PK definition but before it adds table-checks (roughly line 137)
-
Take Hibernate source, change StandardTableExporter to do this ^^, build and use that built jar in your test
|
