Dotnet ef is a very powerful tool, that helps a lot while you are working with DB in your project. I have seen projects that had only ADO.NET, only EF, or only Dapper, but very often you merge at least two of this tech. Something with EF just to have a way to generate and apply migrations with ease. You may like Dapper for its fastness, or ADO.NET for its… rawness (rly, someone?) but EF migrations are a huge time-saver. But there is also a not-so-bright side there.
I usualy use migrations to migrate database structure. You just type
dotnet ef migrations add [MigrationName]
and done. Dotnet-ef builds your app and generates migrations based on DbContext configuration.
To apply it just type
dotnet ef database update
and you are done. Db migrated.
But from time to time there is a case that is not so straightforward and easy. You have to write migrations on your own.
Examples?? Views. Dotnet-ef cannot generate views. Another? Data migrations. It sounds as easy as
generate new migration
write your own script
and you can be sure that it’s so easy, but some things have to be taken into consideration.
In my current project, I had a situation that I had an enum in my entity model. Just three values and default
enum to DB converter so EF core store it as an int in my DB. Just 1, 2, and 3. Cool. Works. But later on, the requirements changed (as they always do :blink:). From now on we can mix these enum values as it if’s a flag. Easy. Add
[Flag] attribute, rewrite values to 1,2 and 4 and… Oh, wait. What about the current data in my DB. Now
4 is the new 3… Ok. Add migration,
update where... and done. Phew, wasn’t so hard :blink:
Some time passes and requirements changed again. We do not need this flag anymore. Ok. New migration, drop the column, done.
The first release passed. And here comes the trouble.
While I wrote that migrations that migrate data from enum to flag (change 3 to 4) I had to specify which column should be updated. And now on this column is gone. Each release failed because my DB validate each script that should be executed. What does that mean to me? I had a script inside an
IF migration does not exist that was invalid, as it refers to the column that no longer exists in DB and it failed all my release with migrations.
To fix that I had to remove that part of the script from migration that manipulates the data in the column that was removed. Maybe there is a better solution for that? If you know, give me a tip in the comments.