sqlmesh migrate is sometimes necessary after upgrading the sqlmesh version. When problems arise later on, one can use sqlmesh rollback to "undo" the migration. When a user wishes to use this command, they also need to revert the sqlmesh version change in their repository (i.e.: git revert or similar), either before or after running the command.
The documentation for the rollback command does not indicate whether it should be run before or after reverting the sqlmesh version (or whether it doesn't matter and using either version will work).
Ideally, the documentation would make it clear which sqlmesh version is expected to be "active" when the command is run as it is related to changing the sqlmesh version as well.
FWIW: after running this command just now, I can confirm that it works after reverting the sqlmesh version; it may also work before reverting.
sqlmesh migrateis sometimes necessary after upgrading the sqlmesh version. When problems arise later on, one can usesqlmesh rollbackto "undo" the migration. When a user wishes to use this command, they also need to revert the sqlmesh version change in their repository (i.e.:git revertor similar), either before or after running the command.The documentation for the rollback command does not indicate whether it should be run before or after reverting the sqlmesh version (or whether it doesn't matter and using either version will work).
Ideally, the documentation would make it clear which sqlmesh version is expected to be "active" when the command is run as it is related to changing the sqlmesh version as well.
FWIW: after running this command just now, I can confirm that it works after reverting the sqlmesh version; it may also work before reverting.