Skip to content

Commit a3ecc6f

Browse files
committed
Update docs/guides/migrations.md
Co-authored-by: Michael Day <mdaytn@gmail.com> Signed-off-by: Adegbite Ayoade <tripleaceme@gmail.com>
1 parent 77a6378 commit a3ecc6f

1 file changed

Lines changed: 1 addition & 0 deletions

File tree

‎docs/guides/migrations.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,3 +58,4 @@ Keep the following in mind before rolling back:
5858
- Only the most recent migration can be rolled back. Restoring consumes the backup tables, so running `sqlmesh rollback` a second time fails with `There are no prior migrations to roll back to.`
5959
- The backups are taken at the moment of migration. Any changes made to the project metadata after the migration, such as plans applied with the newer version, are discarded.
6060
- Like `sqlmesh migrate`, rolling back affects all users of the project and should be issued manually by a single user.
61+
- Rollback is not possible if the migration was run with `--skip-backup`. It also does nothing useful after an upgrade that required no migration, such as a patch release, because no new backup was taken. In that case the backup tables, if present, come from an earlier migration.

0 commit comments

Comments
 (0)