EF Core migration support with Weasel. Closes GH-2149 #2156
+910
−641
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.
updated to the latest Weasel, JasperFx, and Marten
Checkpoint: EF Core related tests are all passing
checkpoint: hooks are in for resource creation of multi-tenancy
Just moved up the timeout on a test
Fix EF Core mapped outbox failing to INSERT envelopes with NULL attempts
Remove .HasDefaultValue(0) from EF Core entity mappings for the Attempts column on IncomingMessage and OutgoingMessage. The HasDefaultValue sentinel caused EF Core to omit the column from INSERT statements when Attempts was 0, but the database column is NOT NULL, causing SqlException. Also clean up test fixtures to use managed migrations instead of manual table creation.
First successful tests
WIP: EF Core migrations
Spiked in the EntityFrameworkCoreSystemPart