* Execute migration files in a [Testcontainers](https://www.testcontainers.org/) or [io.zonky.test:embedded-postgres](https://github.com/zonkyio/embedded-postgres) to get greater insights into if a SQL migration is safe or not. * #17 is an example of a migration that could benefit from context of the table to be dropped * `adding-field-with-default` is another example that could benefit from further context * `changing-column-type` is another example that could benefit from further context ([checking](https://github.com/premium-minds/sonar-postgres-plugin/blob/496c86fe3ecd112225afcc1576c5db52adb1ed1b/src/main/resources/com/premiumminds/sonar/postgres/changing-column-type.md?plain=1#L38) `pg_catalog.pg_cast`) Maybe add an option to disable for situations that the existing migration files don't represent 100% of the state of the database. Open questions: - What is the order to run the migrations ?
adding-field-with-defaultis another example that could benefit from further contextchanging-column-typeis another example that could benefit from further context (checkingpg_catalog.pg_cast)Maybe add an option to disable for situations that the existing migration files don't represent 100% of the state of the database.
Open questions: