Base version for applying change

[ghenadiibatalski]

Hello Roman, this is less an issue but more a question.

1. Do you create and update something like DATABASECHANGELOG collection with already applied patches to prevent failures or damages by accidentially repeating of not idempotent changesets?
2. Is it possible to declare the base state (version/timestamp from the above DATABASECHANGELOG), for what a patch/changeset may be applied?

Regards, Gena

[coldze]

Hi Gena,

Sorry for delay, I'm on vacations right now :)

1. Yes, correct - there is a collection named mongol_migrations_3710611845fe4161b74d2ec5eafe9124. It contains list of changes applied + hash of that change.
2. This tool relies on a sequence of changes, declared in changelog-file - if there is a change (migration) inserted in the middle between already applied migration, it will fail with corresponding message (format: Applied changeSet-set with ID %v after not-applied changes).
   So, directly answering your question - no, right now here is no ability to reference/declare a dependency on another migration or make some kind of tag/versioning.
   Actually, it seems to be a good idea for, at least, removing "old" migrations, ie flattening list of migrations + it will add an extra check for DB integrity before applying migrations.