-
Notifications
You must be signed in to change notification settings - Fork 643
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add unit test to check for pending schema changes #4934
Comments
@chenriksson , which DB do we want to test this on? |
@skofman1 This isn't testing migrations against a DB instance. The test would check if EF would detect schema changes if a new migration were added... comparing the source code against the latest EF migration snapshot. Will keep, but put at P3 |
This was referenced May 7, 2019
joelverhagen
added a commit
that referenced
this issue
May 8, 2019
joelverhagen
added a commit
that referenced
this issue
May 8, 2019
joelverhagen
added a commit
that referenced
this issue
May 8, 2019
joelverhagen
added a commit
to NuGet/ServerCommon
that referenced
this issue
May 8, 2019
Addresses NuGet/NuGetGallery#4934 Similar to NuGet/NuGetGallery#7143
joelverhagen
added a commit
to NuGet/ServerCommon
that referenced
this issue
May 8, 2019
Addresses NuGet/NuGetGallery#4934 Similar to NuGet/NuGetGallery#7143
Done on gallery DB, support requests DB, and validation DB. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Suggested by @joelverhagen to keep migrations and schema changes in sync
Should be possible to programmatically create migration and check. See:
The text was updated successfully, but these errors were encountered: