Flyway follows a simple workflow:

1. Create migration scripts with proper naming convention
2. Place scripts in the configured migration directory
3. Run Flyway migrate command to apply pending migrations
4. Flyway tracks applied migrations in a schema history table
5. Validates migration integrity on subsequent runs
   The tool automatically detects new migrations and applies them in order based on version numbers.

Flyway supports three types of migrations:

1. Versioned Migrations: Applied exactly once, have version numbers
   • Example: V1__Create_user_table.sql
2. Repeatable Migrations: Applied whenever their checksum changes
   • Example: R__Update_user_view.sql
3. Undo Migrations: Used to reverse versioned migrations
   • Example: U1__Undo_Create_user_table.sql

Flyway uses a strict naming convention:
Format: <Prefix><Version>__<Description>.<Suffix>

• Prefix: V (versioned), R (repeatable), U (undo)
• Version: Dots or underscores separated (V1, V1.1, V1_2_1)
• Separator: Double underscore (__)
• Description: Descriptive text with underscores
• Suffix: .sql (default)
  Examples:

V1__Initial_schema.sql
V1.1__Add_user_email.sql
V2__Create_orders_table.sql
R__Update_statistics_view.sql

The info command displays the status of all migrations without applying any changes.
Information provided:

• Current schema version
• List of applied migrations
• Pending migrations
• Migration status (Success, Failed, Pending)
• Description and execution details
  Example output:

Version    | Description       | State   
-----------|------------------|----------
1          | Initial schema   | Success
1.1        | Add user email   | Success  
2          | Create orders    | Pending

Usage: flyway info - Essential for understanding migration state before applying changes.