Arthur Vickers

@ah1508 Making an entity owned indicates that it is part of an aggregate. Aggregates are designed to be loaded and manipulated as a unit. If you want the parent to...

@ah1508 Why do you think this relationship should be owned?

Note from triage: we should not worry too much about table truncations, so doing the thing that works here make sense.

Note for triage: ``` Unhandled exception. System.NotSupportedException: Collection was of a fixed size. at System.SZArrayHelper.Remove[T](T value) at Microsoft.EntityFrameworkCore.Metadata.Internal.ClrICollectionAccessor`3.Remove(Object entity, Object value) at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.InternalEntityEntry.RemoveFromCollection(INavigation navigation, InternalEntityEntry value) at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.NavigationFixer.RemoveFromCollection(InternalEntityEntry entry, INavigation...

Putting this on the backlog to check the first time we create a property accessor. This won't help in all cases because the property can be assigned a new instance...

@FrankIceBass Fixed-size collections, such as arrays, are not supported since EF needs to add elements to them.

@FrankIceBass Typically a collection of one entity type on another entity type. For example, the collection of posts on a blog. This is known as a navigation. See [Relationships](https://docs.microsoft.com/en-us/ef/core/modeling/relationships?tabs=fluent-api%2Cfluent-api-simple-key%2Csimple-key) in...

@FrankIceBass Feel free to open a _new_ issue attach a small, runnable project or post a small, runnable code listing that reproduces what you are seeing so that we can...

Note for triage: we should check the latest recommendations as part of the 7.0 process, since these have changed since the feature was implemented.

Note from triage: also consider information here: https://github.com/dotnet/efcore/issues/28200