wmartins
commented
6 years ago @Harry-027, @sakulstra fixed this for us in #43. I merged that now.
Need to align with @eberhara so we can publish a new version with that. I'm closing your PR in favor of #43.
It has been observed that while running mongration on multiple dbs for multiple migration scripts , the order in which the records get saved in migration collection is not saved as per their given script sequence. Therefore while validation step , comparison for checksum goes wrong and hence throws an error. This PR is to include a safety measure, where migration db records will always be fetched as per the order sequence so that no comparison goes wrong.