Instead of being run just once, repeatable migrations are (re-)applied to a database on migrate every time their checksum changes.

This is very useful for managing database objects whose definition can then simply be maintained in a single file in version control. They are typically used for

• (Re-)creating views/procedures/functions/packages/...
• Bulk reference data reinserts

Within a single migration run, repeatable migrations are always applied last, after all pending versioned migrations have been executed. Repeatable migrations are applied in the order of their description (i.e. alphabetically).

It is your responsibility to ensure the same repeatable migration can be applied multiple times. This usually involves making use of CREATE OR REPLACE clauses in your DDL statements.

Naming

Repeatable migrations have a description and a checksum, but no version. e.g. R__SetDefaults.sql.

Relevant configuration:

• Repeatable SQL Migration Prefix
• SQL migration separator
• SQL migration suffixes

Checksum handling

The filename and checksum are stored in the flyway_schema_history table so we know when the repeatable migrations need to be reapplied.

Example

CREATE OR REPLACE VIEW blue_cars AS
    SELECT id, license_plate FROM cars WHERE color='blue';