Operate
Rollback & restore
Reset a table to an earlier version number or point in time. Destructive - later versions are discarded.
rollback_table and restore_table both return a table to an earlier state.
The only difference is how you name the target:
| Rollback | Restore | |
|---|---|---|
| Target | Version number (version=41) | UTC timestamp ("2026-06-15T14:30:00Z") |
| Use when | You know the exact good version | You know roughly when it was good |
| Find it via | history version column | history timestamp column |
| Destructive? | Yes - discards versions after the target | Yes - discards versions after the target |
| Interface | CLI · REST · MCP · Web UI | CLI · REST · MCP · Web UI |
Heads up
Destructive: neither is a new commit layered on top - all
versions after the target are discarded. The forward history is truncated.
Always read the history and
confirm before running either.
Roll back to a version number
eddytor rollback table eddytor sales orders --version 41PUT /v1/tables/eddytor/sales/orders/rollback/41
Authorization: Bearer edd_live_…rollback_table(table="eddytor.cfg_xxx.<uuid>_orders", version=41)Open the table → History → select the target version → Roll back.
Restore to a UTC timestamp
eddytor restore table eddytor sales orders --timestamp "2026-06-15T14:30:00Z"POST /v1/tables/eddytor/sales/orders/restore
Authorization: Bearer edd_live_…
{ "timestamp": "2026-06-15T14:30:00Z" }restore_table(table="eddytor.cfg_xxx.<uuid>_orders", timestamp="2026-06-15T14:30:00Z")Open the table → History → pick the point in time → Restore.
The timestamp must be ISO 8601 UTC - e.g. "2026-06-15T14:30:00Z". Read
candidate timestamps straight from the
history (they're UTC) rather
than converting from local time.
Safe procedure
- Read the history → identify
the last good version number or timestamp (mind that
OPTIMIZE/VACUUMare versions too). - Optionally diff two versions to confirm what you're undoing.
- Confirm - there's no undo.
- Run
rollback_table(table, version=N)orrestore_table(table, timestamp="…Z"). profile_table+validate_constraints→ confirm the restored state.
What neither can do
- Recover a dropped table -
drop_tabledeletes the data and the Delta log, so there's no history to roll back to. Rollback and restore work only on a table that still exists. - Reach past vacuum - pruned files make older versions unreachable.