Support modifying the value of primary or alternate key properties

In the following location, an exception is raised when attempting to make modifications to a property that belongs to either a primary or alternate key (using the IsKey extension method):

https://github.com/aspnet/EntityFramework/blob/7.0.0-rc1/src/EntityFramework.Core/ChangeTracking/Internal/InternalEntityEntry.cs#L231

I have to ask: why restrict modifications on alternate keys, and why not use IsPrimaryKey here instead?

[AndriySvyryd]

@SidShetye Configuring it as a unique index in EF would be the most accurate approximation. If you don’t use EF to manage the schema you don’t even need to add the index, EF doesn’t use it.

If you do use migrations you can change the generated code to create a key instead.

[SidShetye]

@AndriySvyryd Like I mentioned, we share that database (don’t control the schema; not using migrations etc). We’re just trying to regenerate it’s closest approximation in the C# EF Core 3.0 model. Not having that limitation would allow for a more accurate approximation of the actual SQL database in EF Core.