| Hi Carsten, Bearing in mind I ran into this issue over 5 years ago, the workaround at the time was to hand roll a migration framework for the specific product I was working on. I did consider patching the Hibernate tool, since I had already spent the time to analyze the execution flow. But since I didn't get a response at the time, I wasn't too sure that my solution would get considered, hence it would have been risky to invest time in this. Going forwards, Flyway matured into a widely adopted migration tool, so eventually the product was subsequently ported to use Flyway. However, this approach was facilitated by a migration away from Hibernate as an ORM. I assume that if you use an explicit DDL migration you would also need to hand-map the schema to your object model (or at least have the option of manual mappings to deal with certain impedance scenarios). Hope this helps, Ben |