I’m wondering to what degree–if any–LiquiBase is aware of items in a change set that depend on each other.
My hunch is that LiquiBase leaves this up to the developer.
Here’s what I’m getting at. Suppose I have a changeset, id 1, author me. And suppose in that change set I create a table, and add some columns. Suppose further that one of those columns is a foreign key to another table that…oops! I should mark this change set as id 2, and back up and put in change set id 1 to create that target table.
Are there any shortcut refactorings or other features that make this kind of ordering and dependency management easier?