Question: Rollback to a certain version on a same system about pg-diff HOT 1 CLOSED

Dear @ivanDespot

Thanks for using my tool.
The answer is no.

When I started developing pg-diff I was coming from years using other tools, and all of them implemented classical migration strategy based on Up() and Down() functions.

I don't agree totally with rollback strategy bacause essentially it cannot work in every case and is very dangerous.
From my experience, I never needed to deploy a sql patch that wasn't well tested; this works for me because I know what I did in develop machine and tested again in develop machine before commit my changes.

That's why I choose to not include a rollback strategy, but hey! You can still make a new following patch to revert back changes.

Let me try to explain a possible way to work.
Image that you develop a software based on pgsql.
You should have two databases, one to make changes and very important never connected with software; another one to compare with the above db, make patch, try to apply that patch and connected with your software.
As soon as possible you start debugging or whatelse in order to check your changes.
If changes are OK than you can commit sql patches on source code repository and then share it with your team in case, else delete created patch from your workspace.

In case you use this tool just for databases as diff tool, then you should not apply patch if unsure, but in any case try an approach "fast-forward" always, that in other terms means you should create a new patch to revert back changes.

Make it sense for you?

from pg-diff.