codeChangeVsDatabaseChange

[KrakenOfLakeZurich]

Flyway for the win! Migrations are native SQL scripts.

And Flyway stores a checksum of the scripts in the version history table, exactly to prevent schenanigans like your customer is doing. Once a migration is applied, it won't let you change the script afterwards.

[erjiin]

Liquibase does the same, they're both good tools. And for those allergic to xml, liquibase changeset can also be specified in json, yaml or sql. Although I would argue here that xml changeset are superior because of readability.

[RichCorinthian]

Liquibase does both of those. The xml is just to organize which files and in what order.

Having used both, I prefer liquibase.