You may also like

• 

  Article

  Exploring the Flyway Schema History Table

  Flyway uses a schema history table to track the version of each database, recording in it every versioned migration file applied to build that version. It's worth understanding exactly how Flyway uses this table, the possible dangers of moving it to a non-default location and how to do it safely, if required.

• 

  Article

  What is the Flyway Teamwork Framework?

  The FlywayTeamwork PowerShell framework is designed to help get you started quickly with scripting Flyway migrations for a range of database systems. It introduces a PowerShell task library to help with the scripting of repetitive chores and to generate some of the 'build artifacts' that are often required during team development work. This article explains the basics of the framework's design and provides a demo how to use Flyway to migrate a PostgreSQL database, while generating a high-level narrative of the changes made between versions.

• 

  Article

  Flyway Desktop in Database Development Work: An Overview

  For those new to Flyway Desktop, this article takes a strategic overview of the components of a Flyway Desktop project, how to set up a project for team-based development work, and how we can use the tool in conjunction with a version control system and CI servers to manage a database development and release process.

• 

  Article

  Customizing Database Deployments using Flyway Callbacks and Placeholders

  How to customize a database deployment process using Flyway, demonstrating how to incorporate tasks such stamping a version number into the latest database build, or writing to the SQL Server log.

• 

  Article

  Flyway 6.5.0 Released

  Flyway 6.5.0 is out! This release contains new features and improvements over Flyway 6.4.0. Highlights You can find a detailed list of the changes in the release notes. Toggle schema creation By default, Flyway will attempt to create the schemas provided by the schemas and defaultSchema configuration options. This behavior can be toggled with the createSchemas configuration option. This might be useful when

• 

  Live training session

  Flyway 101: Solving hotfixes and environment specific deployments

  When the process evolves and more people are collaborating with more frequent releases, how can teams stay reactive and continue the agile approach? Using cherry pick to select specific migrations and rollbacks, teams can prioritize certain deployments above others, whilst still working in the designed framework. In addition building additional complexity such as marking scripts already deployed and setting migrations to only be executed against specific locations.