If we require/allow the user to provide the name of their database and it's version then we could skip raising warnings when we know that the warning is not valid for that database and version combination. For example in the description of the "Adding a column with a default value" check we have the note:
Note: This becomes safe in:
Postgres 11+
MySQL 8.0.12+
MariaDB 10.3.2+
If we provided either :postgres, :mysql, or :maria_db along with the version as part of the configuration of excellent_migrations then we could skip raising these warnings in the cases when we know they're safe.
If we require/allow the user to provide the name of their database and it's version then we could skip raising warnings when we know that the warning is not valid for that database and version combination. For example in the description of the "Adding a column with a default value" check we have the note:
If we provided either
:postgres
,:mysql
, or:maria_db
along with the version as part of the configuration of excellent_migrations then we could skip raising these warnings in the cases when we know they're safe.