Hi, in our project, we apparently have a problem or misunderstanding of the relationship between schema changes and data updates.
One team is doing automated tests during build and deployment that executes data migration tests on a development cluster. In those migrations there will be schema changes (adding rows) and subsequent data insertions involving these rows. It seems, there are unpredictable times when the update reaches the cluster *before* the schema change, causing the tests to fail. What can we do to enforce the schema update to have sufficiently happened before the modification is hitting the database? Alternatively, what do others do to handle schema migrations during continuous delivery processes. Jan
