Jeremy Wilson

So, to summarize, unless explicitly told otherwise, the model builder ignores the order in which the properties are declared for the composite key in the anonymous type, it ignores the...

For the benefit of anyone who lands on this page from an Internet search, I wanted to post what I did to ultimately resolve the issue. I used @xuzhg's suggestion...

@xuzhg Thank you for sharing that. The further edification from that issue would indicate that my code needs to be modified to examine `TEntityType` for any `[Column(...)]` attributes on its...

I no longer need this. I devised a clever hack to create type-free calls to extension methods like this: ```csharp /// /// A Type-free version of DbSet.FromSqlRaw /// /// A...

Because of bugs in either OData or EF Core or Automapper (the latest was in EF Core - the SQL it generates is buggy and doesn't work), I was being...

No sir, that is only true for the root most DbSet<> - *<TEntity>* is of Type *<Supplier>* only in that case. (Notice that there is only place in all that...

FWIW, the EF Core bug I mentioned can rather easily be reproduced. 1. Create a database with two tables ```sql create table AppraisalYear ( tax_yr decimal(4,0) not null, certification_dt datetime,...

That makes sense. I realize now that my `GetDbSetForClrType(dbContext, queryInfo.ClrType)` function would only provide access to declared properties, while your approach would grant access to shadow properties as well. In...