dotnet fm rollback all does not work
See original GitHub issueRunning the command below gives me an error
dotnet fm rollback all -p mysql -c "Server=localhost;Database=Db;Uid=root;Pwd=xpto;" -a MyAssmbly.DbMigration\bin\Debug\netcoreapp2.1\MyAssmbly.DbMigration.dll --tag Testing
Unrecognized option '-p'
Am I missing something?
Issue Analytics
- State:
- Created 4 years ago
- Comments:21 (11 by maintainers)
Top Results From Across the Web
dotnet-fm tool
rollback and migrate specific parameters. -m|--transaction-mode <MODE>. Overrides the transaction behavior of migrations, so that all migrations to be executed ...
Read more >How to perform migrations in the package manager?
To run this same migration on a Sql Server 2016 you would run: dotnet fm migrate -p SqlServer2016 -c "server=SQLSERVERINSTANCE;uid=testfm ...
Read more >fluentmigrator
Fluent migrations framework for .NET. ... Migrations solve the problem of evolving a database schema for multiple databases (for ... Rollback-FluentDatabase.
Read more >FluentMigrator changelog - Awesome .NET - LibHunt
DotNet.Cli. Fixes #1123 dotnet fm rollback all does not work . Documentation was also updated in fluentmigrator/documentation#19 @gandarez
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I found the problem. I fixed most of them and there’s one last bug on
rollback
that needs attention. As soon as I finish the tests I do a PR.A rollback command doesn’t support assemblies and/or tags. This seems like an oversight on my side. The
-p
and-c
options are connection options and come directly after therollback
command.Example: