Maurycy Markowski

Currently we use default (lax) mode, should allow to specify strict, so that we throw when path is invalid

Json/Query: translate element access of a json array

1

Something like: ```cs entity.Where(x => x.JsonCollection[0].NestedReference.Name != "Foo") ``` When done in projection, this breaks the ordinal key logic, so we need to force AsNoTracking for these queries. We could...

When json has navigation to the parent entity, it's possible to build linq that would navigate back to the parent, e.g. ``` entity.Select(x => x.OwnedReferece.OwnedNested.Parent.Name) ``` currently we throw as...

We don't support explicitly defined keys for json (yet), the convention would set the property to be a key and it will throw in validation. We should change the convention...

Json/Migrations: flow the json type mapping (or relevant type mapping info) to column in the model differ so we can create correct default value and clr type for json column operation

1

For now the clr type (and default value) are hard-coded. It's not a major issue as we can't really do anything intelligent here, apart from creating a string representation for...

Json: allow mapping json structure to a different column on view and on table

1

When mapping entity type to table and to a view, we allow specifying different column names for both. We could/should allow this for json columns also. Currently the same json...

Added HasPrecision builder methods for temporal period columns and fixed validation so that it can recognize custom precision. Fixes #27228

Fix to #27155 - Average_Grouped_from_LINQ_101 is non-deterministic

2

Added custom asserter that checks results within range, rather than adding sql server specific expected query. For the second test, added proper collection asserter so we can impose the order...

Json Columns initial work

9

Finished work: - basic metadata, - property/navigation access translation, - materialization (entity, collection, with nesting), - honoring json property name attribute for custom naming - validation, Remaining work: - migration,...

Incorrect OData query when collection is mapped as property using converter

2

issue found by @keatkeat87 and originally filed here: https://github.com/dotnet/efcore/issues/19628 Repro: 1.git clone https://github.com/keatkeat87/odata--select-HasConversion-issue.git 2.dotnet ef migrations add init 3.dotnet ef database update 4.F5 5.visit /odata/Products?$select=images Problem here is that images...