Arthur Vickers
Arthur Vickers
@dgxhubbard Nope.
@dgxhubbard `context.Gages.Include("Status")` means for every Gage, also load the Status _relationship_. The relationship consists of one foreign key property and two navigation properties--Gage.Status and its inverse Status.Gages. When loading the...
Triage: Putting this on the backlog to consider translating more than just simple property expressions into index definitions. Also, created #16604, also on the backlog, for specifying the index with...
This issue is in the Backlog milestone. This means that it is not planned for the next release. We will [re-assess the backlog](https://docs.microsoft.com/ef/core/what-is-new/release-planning) following the this release and consider this...
Hard to say what is happening without a repro, but it could just be that you have a `DbSet` property named "RoleUsers", which is then used by convention as the...
@LZzccc222 A couple of things. First, it's notoriously difficult to customize the ASP.NET Core Identity model. It uses a lot of quite obscure mappings. See [Identity model customization in ASP.NET...
Note from triage: low-pri test bug; consider for next MQ.
The underlying problem here is that `CurrentValueComparerFactory.GetComparerType` is used even if a comparer is defined on the principal type for the relationship, regardless of whether the types are potential primitive...
Closing because CLA is not signed.
@eerhardt We tried setting it in the early days of EF Core, and it was a disaster. The main problem was that applications, and some infra, don't expect the connection...