Open nakamasato opened 2 months ago
Migrate lint always replays all migrations on an empty database, so it is expected to run any statement in these files. This is done to bring the db to the current state before applying any new migrations.
This can be somewhat circumvented using checkpoints, but I'm not certain it is applicable in your use case.
I'm using atlas with versioned migration.
When having many large sql files (e.g. manually created DML files with thousands of rows),
atlas migrate lint
takes very long.Even though I use
atlas migrate set
to set the schema as latest as possible,altas migrate lint
is very slow. It would be better ifatlas migrate lint
only checks for the new files to be applied.