Schema Migration History Fix #47
Open
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.
EFCore was passing 'NULL' in as a string for schema when providing a check to check whether the
__EFMigrationsHistory
table existed.At the time the SQL is executed, the context should already be set to the target schema, and theoretically dont ever need to provide the schema criteria.
Fixed the SQL generation to include the schema filter only when the schema provided meets following criteria.
NULL
I ran all unit tests, and everything passes. Verified with a sample test app that only unapplied migrations are applied.