Welcome back

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

or

Don't have an account? Create one

Migrations

Schema drift

Capture schema changes that already landed in the database as a migration file.

Drift means the live database no longer matches the last snapshot. That can happen after Chat applies a change, or after you edit schema in the studio. Fakebase notices and wants a file that describes what already happened.

The Migrations item in the sidebar shows an amber dot when drift is detected.

Save as a migration

  1. Open Migrations. Fakebase prepares a pending file for the drift.
  2. Review the SQL. The file is a record of what is already in Postgres — it is not waiting to run again.
  3. Choose Save as migration. The change is recorded without re-running the SQL.

The status for this file is Waiting for file save until you save it.

Discard instead

If the live change should not stay, choose Discard changes. Fakebase can roll the database back. You can also delete the migration file on disk when you discard.

MigrationsKeep schema changes as SQL files in your repo, in sync with the database you have open.Apply and reviewReview a pending migration and apply it to the database.ChatManage your entire database with natural language.