You may also like

• 

  Article

  Running Structured Database Tests in Flyway

  How to run structured Arrange-Asset-Act-Teardown (AAAT) tests, each time Flyway successfully migrates a database, where you can annotate each test script to specify exactly how the test run should proceed, and then save all results and any errors to a simple ASCII report.

• 

  Article

  Skip Executing Migrations Examples

  As you’ve likely seen we recently released Flyway 7.0.0, containing a lot of new features (read more about what features are available in the blog post). One of the new features is the new Flyway Teams configuration parameter skipExecutingMigrations. This configuration parameter changes migrate to skip executing the contents of the migrations during a flyway migrate or flyway undo, instead just updating the

• 

  Article

  Testing a Flyway Database Migration

  Often, we want to test the new version of a database, produced by a Flyway migration, before committing the new migration file, or to test the same migration run on a number of different databases. This article demonstrates how to do it, by generating and using JSON parameter files to run a series of Flyway actions on any number of databases, on any number of servers.

• 

  Article

  Announcing Flyway/CockroachDB Support

  Earlier versions of Flyway supported simpler schema migrations within a single CockroachDB node. Both Flyway and CockroachDB aim to be simple to use, and we’re delighted that the Cockroach Labs team have worked closely with us to enable Flyway to be just as robust and reliable in scenarios involving many distributed nodes where migrations need

• 

  Article

  Debugging Flyway Callbacks and Migrations that Use Placeholders

  Placeholders come in very handy in Flyway, but troubleshooting the SQL migration and callback scripts that use them can be tricky. This articles demonstrates how to develop, test and debug these scripts in a tool designed for these tasks, such as SSMS, leaving Flyway to do what it's designed for, which is running the scripts.

• 

  Article

  Reviewing SQL Migration Files Before a Flyway Migration

  Your finger is hovering over the 'enter' key to set off the Flyway "migrate" command, but you hesitate. There is a large stack of migration files for this project: don't all these files need to be checked first? Yes, they do, but how? This article demonstrates how, once armed with the file path locations of all the scripts, you can use PowerShell to search them for various purposes such to review them for potentially disruptive changes, or run code quality checks, or to verify documentation standards.