We use flyway with a scala project at work and it does a great job! It was working with ruby on rails that taught me one of the strongest reasons to use psql o

We use flyway with a scala project at work and it does a great job! It was working with ruby on rails that taught me one of the strongest reasons to use psql over over databases - transactional schema changes. If a migration fails I absolutely want the whole migration rolled back so that the schema can be fixed and tried again. Which is why this paragraph is alarming: "First Flyway now autodetects whether a non-transactional statement is present within a migration. If it is, then the whole migration is run without a transaction (and clearly labelled as such in the logs)." Arguably, mostly devs working with psql dont know that its possible to create schema change commands that cannot be transactional, myself included. I imagine creating such a statement 'by accident' is exceedingly rare, but a default of allowMixedMigrations to false seems more sensible to be 'default safe'. I say 'safe' because a broken, half-executed migration can leave a real mess. Thanks for your efforts and for the flyway project!