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.
Resolves #1584 .
Because these are logs, using EF Core directly for the relationship felt weird, because it would create foreign keys and we don't really want those.
So this solution implements a manual join. In fact, a LEFT JOIN, because we still want to show logs that have no fitting UserId set.
The Microsoft docs show how EF Core converts a "GroupJoin(), SelectMany(), DefaultIfEmpty()" combination into a LEFT JOIN.
And this works as expected (notice the LEFT JOIN):