JoasE

I've got the same issue. I don't think it is causing any problems in production, but the warning does keep popping up in our quality gate check on PR's.

I experienced the same problem with the query below: ```csharp var defaultLanguageId = 1; var selectedLanguageId = 2; var query = from defaultTranslation in context.Translations where defaultTranslation.LanguageId == defaultLanguageId let...

@ajcvickers @maumar This issue is currently (part of) the reason my company is delaying the update to EF Core 5 for one of our projects. It seems like something which...

@maumar Thanks for looking into this! I'll discuss this with my team

@TWhidden I'm pretty sure when I tested the workaround @maumar suggested I checked the query that was being sent to the sql server. I remember it being the same query,...

Should probably only be merged once 11.0 is out? I could not find a 11.0 or release branching strategy in the repo and the contributing guide said to target main...

@roji You're right! Sorry about that, should have probably at-least kept it as draft until the other PR was merged. Will do that now. I had some time left over...

TODO: - [ ] Clean up and refactor (code duplication) - [ ] Add JsonPropertyName method in modelbuilding for complex properties and use that for serialization (document source) and query...

I was about to create this issue myself! However, I was going to make it a feature request as I was using the fluent api to configure my entity relations...

I would suggest at-least adding a specific exception for this to help users who run into this determine the issue