Tools: Add -WhatIf parameter to Update-Database

[bricelam]

This would show the migrations that would be applied to the database.

This functionality is also related to #577.

[glen-84]

Maybe --dry-run ? (see here)

[bricelam]

-WhatIf is a first-class concept in PowerShell. We could consider using --dry-run in the DNX (and Console) commands, but I think there is more value in using a common language between the different interfaces.

[glen-84]

Ah, okay, I didn't know about that. It's a bit of an odd name. 😄

I think the DNX commands use lower or possibly camelCase, so I guess it'll be --whatif, --what-if, or --whatIf.

[matt-goldman]

+1 this would be so useful. Also agree with using the -WhatIf (even if in lowercase) as its familiar from PowerShell.

[stap123]

bicep also uses what-if as the syntax for this

[aunikitin]

Hello, any updates?

[bricelam]

No updates. Today you can use Get-Migration to see which migrations are pending and Script-Migration to see the SQL they'll generate.

[EliveltonRepolho]

This is still not helpfull using the Script-Migration to see the SQL, because it don't show the script for only not applyied migration, it shows the script starting from a migration I have to provide, so on large teams where we frequently deploy and you have a scenario where you have some migrations that are applied and some there are not mixed, you have the create a program to see all peding script.

Would be very helpfull to see a --dry-run option, since EF already does it internally to apply only the pending.

My example is something like this:

1231(Timestamp)_Migration1.cs -- Applied
1232(Timestamp)_Migration2.cs -- NOT Applied
1233(Timestamp)_Migration3.cs -- Applied
1234(Timestamp)_Migration4.cs -- NOT Applied
1235(Timestamp)_Migration5.cs -- Applied

I want to see only the "NOT Applied" scripts, I need to run 2 scripts in this case, but as it grows this become less efficient