Arthur Vickers

@codetuner Proxies are associated with the context instance that created them unless they are tracked by a different context instance, in which case the proxy instance becomes associated with that...

@codetuner I think it's very unlikely that we will change these behaviors; this is all very much by design. See [Change Tracking](https://learn.microsoft.com/en-us/ef/core/change-tracking/) in the docs for more details.

@codetuner The problem with `AddOrderLine3()` is that the same context instance is being re-used, and it is already tracking the previous product instance. Consider using a new DbContext instance for...

For AddOrderline5, the call to `context.OrderLines.Add(line);` will mark all entities in the graph as `Added`. This is because none of the entities are already tracked, and `Add` always marked untracked...

Note from triage: do it once we update to use .NET preview 1 in the build.

/cc @maumar Can you take a look at this? Could be a dupe.

Note for team: still repros on latest daily; regression from 7. Output from 8: ``` dbug: 2/12/2024 10:33:44.583 CoreEventId.QueryCompilationStarting[10111] (Microsoft.EntityFrameworkCore.Query) Compiling query expression: 'DbSet() .Select(itm => itm.CityName .Concat("- A string"))'...

@21r8390 It's possible we will backport this to a patch, but not decided yet. /cc @SamMonoRT

@rogereeno Can you test with the [daily builds](https://github.com/dotnet/efcore/blob/main/docs/DailyBuilds.md) to verify that your issue is fixed there. The more people who do this, the more confidence we will have that patching...

@oleggolovkov There is a possibility that we will patch this, but we need enough people to report back that the daily build is working first.