In the "Removing Relationships" I suggest clarifying ICollection.Remove(T) vs. EntityFrameworkCore.DbSet.Remove(T).
Note that there is no "Deleting Data" section in this docs section, since deletions happen when saving - but shouldn't the docs first advise the reader that to delete, they most likely should use DbSet.Remove(T) rather than deleting the relationship - which has its own big section? This is likely to be important to anyone who reverse engineered from a database without cascade delete configured for required FK relationships.
Thanks!
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: 0f0fb981-4dec-7ff7-817b-6606f620b875
Version Independent ID: c7517e7d-f011-a24c-53da-913771913998
Note for triage: The change tracking docs have a lot more in-depth discussion of these concepts. We should probably either consolidate in one place, or at least link more explicitly.
In the "Removing Relationships" I suggest clarifying ICollection.Remove(T) vs. EntityFrameworkCore.DbSet.Remove(T).
Note that there is no "Deleting Data" section in this docs section, since deletions happen when saving - but shouldn't the docs first advise the reader that to delete, they most likely should use DbSet.Remove(T) rather than deleting the relationship - which has its own big section? This is likely to be important to anyone who reverse engineered from a database without cascade delete configured for required FK relationships.
Thanks!
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.