Research and possible start of a fix for issue 1337 #1350
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 includes a test for issue #1337
And possible part of a fix, but I stumbled upon another roadblock.
With the current fix, I was able to get the foreign keys of the
Email
entities filled properly with their respective custId, and even inserted/merged into the database, but then an exception is thrown when trying to read the output from that operation, asDbContext.Set<Email>().FromSqlRaw()
is used for that, andDbContext.Set<TEntity>
isn't supported for owned types.Not sure how to tackle this... but I thought I'd throw this out there already in case someone else has ideas?