Welcome back

Sign in with GitHub, Google, or your email and password

or

Don't have an account? Create one

Migrations

Migrations

Keep schema changes as SQL files in your repo, in sync with the database you have open.

Migrations are how Fakebase remembers schema work. Each change becomes a SQL file in your project. The Migrations page is the journal: what has been applied, what is still pending, and whether the live database still matches the files.

If you have not linked a folder yet, start with Set up migrations. After setup, an empty journal reads No migrations yet. Create one when your schema changes.

Reviewing migrations in Fakebase Studio

Statuses

  • Applied — this file has been recorded on the database.
  • Pending to be applied — the SQL is on disk and still needs to run.
  • Waiting for file save — the database already changed (from Chat or the studio). Save it as a migration, or discard it. See Schema drift.
  • Modified — an applied file was edited on disk. Restore it before you apply, bundle, or revert.

An amber dot on Migrations in the sidebar means the live schema and the snapshot have drifted.

Review a file

Select a migration to open it. SQL Migration shows the file. Schema Overview shows what was added, removed, changed, or left alone.

From here you apply pending files, capture drift, or manage history — restore, bundle, delete, or relink the folder.

Set up migrationsLink a migrations folder to your database so Fakebase can track schema changes.Apply and reviewReview a pending migration and apply it to the database.Schema driftCapture schema changes that already landed in the database as a migration file.Manage historyRestore, bundle, delete, and relink migrations in Fakebase Studio.