Add support for simple background migration jobs - #873
Merged
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
1 participant
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 introduces support for background migration jobs that run alongside Refresh, have access to all of our database code, and don't block on startup.
They can filter and order a table, then iterate over the results. An example migration is provided for the unit tests.
This is good for migrations that we can't easily write with raw SQL or EF migration code, or can take a long time. They're also database agnostic as they're written in C#.
Ideally, and I've done some preparatory work for this but I'm not sure if it's exactly working, is that they can also be terminated as they run and cleanly be picked back up.
This isn't the system that will be used to import the dry archive - that will most likely be a different project. This is only marked under the dry archive milestone because it's preparatory work for #618.