[Bug?] Why is `UniqueConstraintException.ConstraintProperties` collection null for alternate key?

[voroninp]

I'm witnessing a weird behavior.

If I try to insert an entity with the same PK, I get Common.UniqueConstraintException with ContratintProperties: ["Id"].
If I declare a nuique index on property and try to insert an entity with the duplicate value, I get Common.UniqueConstraintException with ContratintProperties: ["Property"].
However, if I declare an alternative key instead of the index, I get Common.UniqueConstraintException with ContratintProperties: null.

Code to reproduce:

using EntityFramework.Exceptions.PostgreSQL;
using Microsoft.EntityFrameworkCore;
using Testcontainers.PostgreSql;

var container = new PostgreSqlBuilder().WithDatabase("app-db").WithPortBinding(5555, 5432).Build();
await container.StartAsync();

var ctx = new AppDbContext(container.GetConnectionString());
await ctx.Database.EnsureCreatedAsync();
var e = new Entity { Property = 1 };
await ctx.AddAsync(e);
await ctx.SaveChangesAsync();
ctx.Entry(e).State = EntityState.Detached;

e = new Entity { Property = 1 };
await ctx.AddAsync(e);
await ctx.SaveChangesAsync();

Console.ReadKey();

public sealed class AppDbContext(string connectionString) : DbContext()
{
    protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
    {
        optionsBuilder
            .UseExceptionProcessor()
            .EnableSensitiveDataLogging()
            .UseNpgsql(connectionString);
    }

    protected override void OnModelCreating(ModelBuilder modelBuilder)
    {
        modelBuilder.Entity<Entity>(b =>
        {
            //b.HasIndex(p => p.Property).IsUnique();
            b.HasAlternateKey(p => p.Property);
        });
    }
}

public sealed class Entity
{
    public int Id { get;  set; }

    public int Property { get; set; }
}

[Giorgi]

Can you post your db model including the context or better yet, provider a repro project?

[voroninp]

MissingProperties.zip

Here it is.

[gilmar-sales]

I'm having the same problem in Oracle, by debugging I've found that it's because of similar index names like: IDX_USER and IDX_USER_NAME.

Maybe after consider get the first index ordering descending by index name length, to avoid this scenario which another index contains the index that has thrown UniqueConstraintException.

[gilmar-sales]

Another thing to consider: In my case (Oracle) the SchemaQualifiedTableName is not present in the exception message.

[Giorgi]

@gilmar-sales That's a good idea, want to send a PR?

[gilmar-sales]

Another thing to consider: In my case (Oracle) the SchemaQualifiedTableName is not present in the exception message.

This is because of the builder.HasDefaultSchema() method. Adding a default schema to DemoContext causes 40+ tests to fail.