Matthias Wessendorf the problem is that in this case it would happily create the tables while on H2 and satisfy your need, but would completely bork the other databases.

After looking to the possible options, we could (not sorted by preference, just listing them)

A) prepare migrations for H2
B) generate a development and a production war, with the correct setting applied
C) drop H2 support
D) enable auto schema migration like keycloak does, but with a special flag to enable it (I'd be 300% against enabling this by default)

Thoughts?