What is the purpose of the RoundhousE RestoreRun mode?

Question

According to the documentation , RoundhousE has 3 modes:

• Normal
• DropCreate
• Restoreun

The first 2 are clear, but I don't understand RestoreRun Mode and the benefits it offers in Production:

Once you switch to production, you switch from DropCreate to RestoreRun if your database is small enough. . If not, you can continue the idea of ​​a service mode by switching to a new script name that you are making changes to. You can also back up the structure only (and some search data if you use a tool like LiteSpeed) and restore from that.

I had the impression that RestoreRun would restore the database backup before running the migration scripts. If so, I could see that it is useful in development, where I repeatedly test my new scripts, but I don’t see the purpose for creating it.

Here are my questions:

• Do I really not understand the purpose of RestoreRun?
• What is a sample use case of RestoreRun for a production deployment?
• Are there any other differences than starting db recovery between RestoreRun and Normal?

Any understanding of this would be greatly appreciated.

Answer 1

. , RestoreRun . , , db .

Answer 2

, , , , , . RoundhousE:

Q: RestoreRun , Normal, , ?

A: , runAfterCreate. /restore/restorefrompath = VALUE /restorecustomoptions = VALUE/restoretimeout = VALUE. https://github.com/chucknorris/roundhouse/wiki/ConfigurationOptions

Answer 3

, rh.exe , .

"\ shared\MSBuild\Roundhouse\rh.exe" -w/restoretimeout 36000/cs=%server.connectionstring%/f=%sql.files.directory%/vf=%version.file%/vx =% version.xpath%/r=%repository.path%/env =% environment%

.

For your work, I want something like above. Any new scripts that you do not want to run during production must have ENV.% Environment% .sql, so when the environment is set up for production, these scripts are not executed.