Category Archives: Без рубрики

✅ Short Answer Yes, you can write migrations in Java by implementing the JavaMigration interface or extending BaseJavaMigration.This allows you to write complex, logic-driven database changes in code, including loops, conditional logic, or calling other APIs. 🔍 How to Write … Continue reading →

**flyway.migrate()** is the core method in Flyway used to apply pending migrations to your database. It scans the migration files, checks which ones haven’t been applied (based on flyway_schema_history), and executes them in order. 🧠 When Would You Use It? … Continue reading →

If you rename a Flyway migration file that was already executed, Flyway will treat it as a new migration and might: ❌ Try to re-run it (if version number changes) ❌ Throw a checksum error (if only filename changes) ✅ … Continue reading →

Versioned migrations run once, in a strict order, and never again. Repeatable migrations can run multiple times — they’re re-applied whenever the file changes. They serve different purposes in managing your database schema. 🔍 Detailed Comparison Feature Versioned Migrations Repeatable … Continue reading →

The flyway_schema_history table is a metadata table automatically created by Flyway in your database.It records which migrations have been applied, in what order, by whom, and when — ensuring each migration is executed exactly once. 🔎 Detailed Explanation When you … Continue reading →

Flyway uses a structured naming convention for migration files: ✅ The V stands for versioned migration✅ A double underscore __ separates the version from the description✅ The description is free-form (no spaces) and helps identify the purpose✅ The file must … Continue reading →

Flyway is a lightweight, Java-based database migration tool that helps you version, manage, and automate schema changes using plain SQL or Java migration scripts. It’s simple, fast, and widely used in microservices, CI/CD pipelines, and Spring Boot projects. 🔎 Detailed … Continue reading →

✅ Short Answer The logicalFilePath is an identifier for a changelog file that Liquibase uses internally to track changesets — instead of the physical file path. It helps ensure consistent tracking of changesets even if the file is moved, renamed, … Continue reading →

✅ Short Answer **<include>** lets you include one specific changelog file into another **<includeAll>** lets you include all changelogs from a folder, automatically This helps you modularize and organize your migrations across many files.. 🔎 Detailed Explanation 🔹 include Used … Continue reading →

✅ Short Answer You apply a Liquibase migration using the update command from the CLI: This command tells Liquibase to: Connect to your database Read the changelog file Apply any changesets that haven’t been run yet 🔎 Step-by-Step Command Line … Continue reading →