lorenzbaier

i think I found the commit which breaks this https://github.com/liquibase/liquibase/commit/2b1c363e7f998bcdb1e4a6c66906a0e2c2226f77 in `SnapshotControl` (where the types are filtered https://github.com/liquibase/liquibase/commit/2b1c363e7f998bcdb1e4a6c66906a0e2c2226f77#diff-8103e5b2a72eeba8cd3b9dbd302a1e3199c99fb2eebb8f5de71b817424f74aaeR133) this doesn't work together with https://github.com/liquibase/liquibase-hibernate/blob/33fa3cef887a649a6138e8a9765da05c1b6a7a56/src/main/java/liquibase/ext/hibernate/database/HibernateDatabase.java#L333 because then the CatalogSnapshotGenerator (https://github.com/liquibase/liquibase-hibernate/blob/33fa3cef887a649a6138e8a9765da05c1b6a7a56/src/main/java/liquibase/ext/hibernate/snapshot/CatalogSnapshotGenerator.java#L21) is...

this issue is related to https://github.com/liquibase/liquibase-hibernate/issues/708 it breaks because the `Catalog` type is filtered out now because `HibernateDatabase` does not support it, but previously has `setDefault(true)` on the Catalog anyway...

i have the same issue but it seems like it orignates from not even setting the constraint name in the DDL hibernate generates: `create table "point" ... unique ("number", "parent_version_identifier"),...

@gavinking is there a changelog which reports this new behaviour of hibernate not generating the constraint names anymore?

@gavinking but the auto generated constraint names are obviously missing and i do not want to explicitly state them all

i created an issue on hibernate https://hibernate.atlassian.net/browse/HHH-17921

Ok thanks for the quick reply, I will try the workaround. Is there any good documentation which covers this? because I could not find any but I think it is...