I tried using the same migration set for multiple database providers, and that worked out with
.net core 2, and in .net core 3 and ef core 3, it does not work as it adds a .hasColumnType() to migration Design class for each migration, and the column type varies from database provider to another, which makes the migration fail when trying to apply it
at a different database from the one it was used in the dbcontext when creating the migration.
Is there a way to use same migration set for different database providers in .net core 3, or this feature is no longer available?
Kind Regards,
Hani Draidi