It turned out that so-called transactional DDL support is disabled in Play evolutions by default. That's documented; to enable it, we need to set evolutions.autocommit=false.
I think that we need to do that to avoid further confusion on failed evolutions in our code base.
I have reproduced the issue #198 and checked that it won't reappear with that change: the database doesn't get changed at all if any evolution fails.
It turned out that so-called transactional DDL support is disabled in Play evolutions by default. That's documented; to enable it, we need to set
evolutions.autocommit=false
.I think that we need to do that to avoid further confusion on failed evolutions in our code base.
I have reproduced the issue #198 and checked that it won't reappear with that change: the database doesn't get changed at all if any evolution fails.
Closes #198.