Maurycy Markowski

there is a problem with this fix, some tests regress into data corruption (from invalid token now), need to investigate in-depth. failing tests for NTWIR Json_branch_collection_distinct_and_other_collection - NRE Json_collection_distinct_in_projection -...

@roji @ajcvickers new version up

@ajcvickers you can't project a "naked" owned type in a tracking query scenario. https://github.com/dotnet/efcore/issues/31047, so we always have the parent entities and they include everything in the correct order.

Simplified: ```cs #nullable enable [ConditionalFact] public void Repro32911() { using var ctx = new MyContext(); ctx.Database.EnsureDeleted(); ctx.Database.EnsureCreated(); ctx.Add(new Offer { Variations = [ new Variation { Payment = new Payment(120,...

query we generate is wrong: ```sql SELECT TOP(2) [o].[Id] FROM [Offers] AS [o] WHERE [o].[Id] = 1 ORDER BY [o].[Id] SELECT [s].[Id], [s].[NestedId], [s].[OfferId], [s].[payment_brutto], [s].[payment_netto], [s].[Id0], [o0].[Id] FROM (...

problem is during apply projection. In `GenerateComplexPropertyShaperExpression` we loop through properties of the complex type to generate corresponding column, but we don't have enough information to create the correct column....

reopening for possible patch

for queries with JSON (when we are streaming), we still need to go through the entire stream even if we have an entry in the change tracker already. In case...

There is a fundamental problem with using NTWIR and not projecting root entity. For Tracking queries we don't allow that (i.e. we throw), but currently for NTWIR we do. When...

We can either do sophisticated ordering of which elements get materialized before which (i.e. full collections before individual element accesses), or block the scenario where you don't project root in...