Micronaut Flyway

In this tutorial, you'll learn about Fix Micronaut Flyway Migration Not Applying. We cover key concepts, practical examples, and best practices.

The Problem

Flyway migrations do not run on application startup in Micronaut.

Quick Fix

Add Flyway dependency

Wrong:

<!-- No flyway -->

Output:

No migration execution

Right:

<dependency>
  <groupId>io.micronaut.flyway</groupId>
  <artifactId>micronaut-flyway</artifactId>
</dependency>

Output:

Flyway enabled

Configure Flyway

Wrong:

# No flyway config
flyway.datasources.default.enabled=true

Output:

Not enabled

Right:

flyway:
  datasources:
    default:
      enabled: true
      locations: classpath:db/migration

Output:

Flyway configured

Use correct migration naming

Wrong:

V1__init.sql // Correct naming

Output:

Right:

Output:

Flyway requires V{version}__{description}.sql naming

Prevention

• Add micronaut-flyway dependency
• Configure flyway.datasources.default.enabled=true
• Place migrations in db/migration directory

Common Mistakes with flyway

1. Using return to exit a function early instead of wrapping a pure value in the monad
2. Mixing let bindings with <- bindings in do notation, producing type errors
3. Overlapping type class instances that cause GHC to reject the program with ambiguous dispatch errors

These mistakes appear frequently in real-world MICRONAUT code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

This quick fix is part of the DodaTech Spring & JVM ecosystem series. Built by the developers of Doda Browser, DodaZIP, and Durga Antivirus Pro.