Change an entity
Add a field, rename a column, create a table. Write Java as usual.
Run migrax generate
Get readable SQL and a rollback script, checked for risky statements.
Run migrax migrate
Apply it from the command line, in CI, or when the application starts.
See it in 30 seconds
Add a field to an entity, and Migrax writes the SQL.
The migration is plain SQL you can read, review and commit, with a rollback script next to it. Nothing is hidden: you can edit every statement before it runs.
Why teams use Migrax
Everything a migration needs, checked before it reaches production.
-
Migrations written for you
Change an entity, run
migrax generate. Tables, columns, keys, indexes, join tables, element collections, sequences and inheritance come out exactly as Hibernate maps them. -
Checked before production
Every migration is linted for statements that lock big tables, fail on existing rows or break running instances.
migrax verifyhas your Hibernate version validate the result. -
Rollback included
Each generated migration comes with a rollback script, and
verifyproves it works by rolling everything back and forward again. -
Asks before it loses data
A dropped column that looks renamed? Migrax asks, and renames it so the data stays. Drops only happen when you say
--allow-destructive. -
Catches manual changes
migrax driftcompares the live database with what your migrations produce and lists every difference, including columns someone made narrower. -
Zero setup
Run it in your service folder. It compiles the project, finds the dependencies and reads the database settings from your application configuration.
Works with your stack
Detected automatically. No plugin configuration needed to get started.
Ready when your next entity changes¶
Install the command line tool in a minute, then run it in any service folder.