Features & workflows
Applying a plain-SQL file
Open any .sql file, read a per-statement safety plan, rehearse it on a throwaway copy, then apply it.
You do not need an ORM to apply a migration. Open any .sql file — a hand-written schema change included — and AddisDB breaks it into statements and shows you what each one will do before anything runs.
The safety plan
Each statement is classified and listed in order, with destructive operations flagged. You see the whole plan up-front, so a DROP buried on line 200 of a long file is something you notice before you apply, not after.
Rehearse it first
Optionally dry-run the file against a throwaway clone of your database. The clone is disposable, so a migration that fails half-way fails somewhere that does not matter — and you find out which statement broke before you touch the real thing.
Applying
Applying goes through the same safety gate as every other write, so a read-only or production connection stays protected until you deliberately grant edit access. AddisDB shows that state before you start rather than letting the apply fail at the last step.