Migrations
Manage history
Restore, bundle, delete, and relink migrations in Fakebase Studio.
Use these when you need to move the journal — not for the everyday apply loop. Open Migrations with a folder already linked.
Restore to an earlier migration
On an older Applied migration, choose Revert in the header, or Restore to here in the list. Review the rollback SQL, then Restore database. Later migrations are unapplied.
Bundle pending files
Shift-click a contiguous range of Pending migrations, then Bundle. Fakebase merges them into one file. The bundled file is not applied automatically — apply it when you are ready.
Delete or discard
Delete migration removes the last file in the journal. For a drift file that should not be kept, Discard changes can roll back Postgres. Optionally delete the file on disk at the same time.
If an Applied file was edited on disk, Fakebase marks it Modified. Restore that file before you apply, bundle, or revert.
Change folder or reset
Change folder points this database at a different migrations directory.
Reset migrations unlinks the journal. You can delete the files on disk. Reset does not undo schema that is already in PostgreSQL. Set up again from Set up migrations when you are ready.