Arthur Vickers comments

Results 1127 comments of


                                            Arthur Vickers

Do not track after SaveChanges()

@Giancarlos This issue is not related to AsNoTracking--that will tell EF not to track entities returned from the query. This issue is about SaveChanges ignoring store-generated values for already tracked...

Do not track after SaveChanges()

Notes from triage: - Perf benefit seems minimal based on recent testing--if you are seeing otherwise, then please post details. - Clearing the change tracker after saving changes can be...

Copy/upsert data across tables in bulk (INSERT ... SELECT)

@voltcode This issue is in the Backlog milestone. This means that it is not planned for the next release (EF Core 8.0). We will [re-assess the backlog](https://docs.microsoft.com/ef/core/what-is-new/release-planning) following the this...

Include() on owned types does not work when placed after Where()

Note for triage: this is a case where there is an owned type with navigations to *non-owned* nested types. A query without Includes treats these as auto-included: ```sql SELECT [p].[Id],...

Include() on owned types does not work when placed after Where()

@romfir Good catch; so the query is not correct either.

SQL Server: DateTime.DayOfWeek translation

@cyptus This issue is in the Backlog milestone. This means that it is not going to happen for the 3.0 release. We will re-assess the backlog following the 3.0 release...

Discriminator on derived type is being incorrectly updated with integer value of enum (EF Core CosmosDB provider)

Poaching. Confirmed bug, still repros on 9.

EFCore Delete And Add will merge to Update, and throw NullReferenceException

Duplicate of #30705

Consider allowing instantiation with non-parameterless constructor in queries, treating it the same as initializers

This issue is lacking enough information for us to be able to fully understand what is happening. Please attach a small, runnable project or post a small, runnable code listing...

Consider allowing instantiation with non-parameterless constructor in queries, treating it the same as initializers

Note for query folks: this isn't about using a primary constructor or record, but rather projecting to a parameterized constructor of a non-mapped type. Do we have a dupe/common message...