Should UniqueConstraintException include primary key details

[kimsagro1]

Given the following

public class Person(Guid personId)
{
    public Guid PersonId { get; init; } = personId;
}

Trying to insert two people with the same PersonId (Guid.Empty in this instance) results in the following UniqueConstraintException

EntityFramework.Exceptions.Common.UniqueConstraintException: Unique constraint violation
 ---> Microsoft.Data.SqlClient.SqlException (0x80131904): Violation of PRIMARY KEY constraint 'PK_People'. Cannot insert duplicate key in object 'dbo.People'. The duplicate key value is (00000000-0000-0000-0000-000000000000).

However the ConstraintName and ConstraintProperties are NULL

If we include primary keys in the uniqueIndexes (rough code below)

if (uniqueIndexes == null)
{
    var indexes = context.Model.GetEntityTypes().SelectMany(x => x.GetDeclaredIndexes().Where(index => index.IsUnique));
    var mappedIndexes = indexes.SelectMany(index => index.GetMappedTableIndexes(), (index, tableIndex) => new { tableIndex.Name, index.Properties });

    var primaryKeys = context.Model.GetEntityTypes()
        .Select(x => x.FindPrimaryKey())
        .Where(x => x is not null)
        .Cast<IKey>()
        .Select(primaryKey => new { Name = primaryKey.GetName()!, primaryKey.Properties });   

    uniqueIndexes = mappedIndexes
        .Union(primaryKeys)
        .ToDictionary(arg => arg.Name, arg => arg.Properties);
}

Then the UniqueConstraintException now has ConstraintName=PK_People and ConstraintProperties=PersonId

[Giorgi]

I think that would be nice.