It appears that preconditions can only check the state of the database as it existed at the beginning of the Liquibase run. Is that on purpose?
For example, suppose we have the following sequence:
- transactional changeset: createTable A
- transactional changeset: check to see if A exists () and add a column
On the first run, the precondition guarding the second changeset will not detect that table A exists, correct?
Is that a flaw, or a deliberate design decision?