Does Flyway's undo command reliably reverse schema changes without data loss?

Problem Statement

Flyway's undo command is designed to reverse applied migrations, but its reliability when handling complex schema changes remains unclear. The feature requires developers to manually write undo scripts, which introduces human error risk and lacks automated detection of data-destructive operations.

Constraints and Uncertainty

The core challenge lies in determining whether Flyway can guarantee complete and safe reversal of schema modifications, particularly when migrations involve data transformations, column type changes, or constraint modifications. Documentation does not clearly specify the validation mechanisms available to ensure undo operations maintain data integrity.

Specific Questions

• Can Flyway detect and flag potentially unsafe undo operations before execution?
• What safeguards exist to prevent partial or incomplete schema reversal during undo?
• How should teams structure their undo scripts to handle interdependent schema changes?