Docs/Configuration/History & snapshot tables
OSS
History & snapshot tables
DBLift keeps its own state in the database it manages. Two tables, both renameable, both created on first use.
Keys
These sit at the top level of the file, not inside a section, and can each be set from the environment.
| Key | Default | What it holds |
|---|---|---|
history_table | dblift_schema_history | One row per applied migration: version, description, type, checksum, who applied it, when, how long it took, and whether it succeeded. |
snapshot_table | dblift_schema_snapshots | Captured schema snapshots, each with its checksum and the model it recorded. |
max_snapshots | 1 | How many snapshots to retain. When a capture pushes the count past this, the oldest is deleted. |
Renaming is a migration in itself
Changing history_table against a database that already has history does not move the rows. DBLift will find no history under the new name and treat every applied migration as pending. Rename the table in the database in the same change.