this post was submitted on 31 Mar 2026
20 points (95.5% liked)
Programming
26304 readers
703 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Working on an extension for Entity Framework Core that primarily lets you commit stored procedures, database functions, and other custom SQL commands to the DbContext model. Changes to these commands will be scaffolded as database migrations.
If you currently use EF Core for configuring a database code first, you have to create a migration and then add any custom SQL commands to the migration code.
That works fine until you've got a bunch of old migration classes you want to clean up/consolidate. Then you have potentially dig through a bunch of files to look for any migration files that contain custom SQL to make sure you don't accidentally delete them. It's one of those things that most likely won't be a problem but when it is, it's a big problem.