Changeset run by --include treated as different than the same changeset run by --migration
Description
I have a migration file that includes a changeset (A). I ran db migrate on the file using the --include option and specified the context. Now I have a database with the changes made from that changeset. The command I ran is below: java -jar *.jar db migrate config.yml --include 1.4.0
I have since added another changeset (B) to the migration file, however this time I used the --migration file and specified the migration file path. Liquibase seems to think that the changeset (A) that existed in the file when I previously ran db migrate with the --include options has not been run, even though it has been. I ran the following command: java -jar *.jar db migrate config.yml --migration migrations.1.4.0.xml
It seems that the same changeset from the same file is considered different when run using --include vs --migration.
I have a migration file that includes a changeset (A). I ran db migrate on the file using the --include option and specified the context. Now I have a database with the changes made from that changeset. The command I ran is below:
java -jar *.jar db migrate config.yml --include 1.4.0
I have since added another changeset (B) to the migration file, however this time I used the --migration file and specified the migration file path. Liquibase seems to think that the changeset (A) that existed in the file when I previously ran db migrate with the --include options has not been run, even though it has been. I ran the following command:
java -jar *.jar db migrate config.yml --migration migrations.1.4.0.xml
It seems that the same changeset from the same file is considered different when run using --include vs --migration.