implement database migrator and DbUp script execution#1617
Open
mahmoudsallam2111 wants to merge 1 commit into
Open
implement database migrator and DbUp script execution#1617mahmoudsallam2111 wants to merge 1 commit into
mahmoudsallam2111 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces a standalone Migrator console application and a Shared.SQLScripts class library to significantly improve the solution's database initialization and deployment strategy. By moving migration execution out of the Web project startup and into a dedicated executable, we achieve better separation of concerns and enable enterprise-grade CI/CD patterns, such as running database migrations as pre-deployment jobs. To address the limitations of Entity Framework Core in managing raw SQL assets, this implementation integrates the DbUp library, allowing developers to cleanly partition and execute raw SQL scripts into "everytime" deployments (ideal for Stored Procedures and Views without journaling) and "onetime" deployments (ideal for Seed Data and complex schema changes tracked via a journal table). Additionally, the migrator's dependency injection is fully aligned with the project's multi-provider strategy via C# preprocessor directives, and a minor compilation constant issue in the build properties was resolved to ensure EF Core generates accurate data types for SQL Server instead of falling back to SQLite. Ultimately, this architecture provides a highly reliable, fail-fast migration pipeline that protects the application from starting in an inconsistent state.