EFCore.ComplexIndexes.PostgreSQL 2.0.0

Index support for complex type properties in EF Core migrations — the missing piece for value object-driven architectures.

EF Core 8.0 introduced complex properties, but migration tooling doesn't automatically generate indexes for these nested value objects. This NuGet package bridges that gap with a clean, fluent API for defining single-column, composite, unique, and filtered indexes directly on complex type properties.

Why it matters:

• Value Object Indexing: Seamlessly add database indexes to properties buried inside complex types (e.g., Person.EmailAddress.Value)
• DDD-Friendly: Supports the Domain-Driven Design pattern of encapsulating logic in value objects without sacrificing database performance
• Migration-Aware: Automatically generates proper CREATE INDEX and DROP INDEX operations during EF Core migrations
• Flexible Filtering: Supports SQL WHERE clauses for filtered indexes (e.g., soft deletes)
• Composite Indexes: Define multi-column indexes spanning both scalar and nested properties with a single, intuitive expression

Package	NuGet	Description
EFCore.ComplexIndexes		Core library — single-column, composite, unique, and filtered indexes on complex type properties. Works with any EF Core relational provider.
EFCore.ComplexIndexes.PostgreSQL		PostgreSQL extensions via Npgsql — adds GIN, GiST, BRIN, SP-GiST, and Hash index methods, operator classes, covering indexes (INCLUDE), concurrent creation, and nulls-distinct control.

Which package do I need? Install only the core package if you use SQL Server, SQLite, or any provider where the default B-tree index type is sufficient. Add the PostgreSQL package when you need PostgreSQL-specific index types — it includes the core automatically.

Quick Example:

builder.ComplexProperty(x => x.EmailAddress, c => 
  c.Property(x => x.Value)
   .HasComplexIndex(isUnique: true, filter: "deleted_at IS NULL")
);

builder.HasComplexCompositeIndex(x => new { x.Name, x.EmailAddress.Value }, isUnique: true);

PostgreSQL Samples:

// GIN index on a JSONB complex property
builder.ComplexProperty(x => x.Metadata, c =>
    c.Property(x => x.Tags)
     .HasComplexIndex(ix => ix.UseGin())
);

// Unique GiST index with filter
builder.ComplexProperty(x => x.Location, c =>
    c.Property(x => x.Coordinates)
     .HasComplexIndex(ix => ix
         .IsUnique()
         .UseGist()
         .HasFilter("deleted_at IS NULL")
     )
);

// GIN with operator class
builder.ComplexProperty(x => x.Profile, c =>
    c.Property(x => x.Data)
     .HasComplexIndex(ix => ix
         .UseGin()
         .HasOperators("jsonb_path_ops")
     )
);

// Composite BRIN index
builder.HasComplexCompositeIndex(
    x => new { x.CreatedAt, x.Sensor.ReadingValue },
    ix => ix.UseBrin()
);

// Simple cases still work without the satellite
builder.ComplexProperty(x => x.Email, c =>
    c.Property(x => x.Value)
     .HasComplexIndex(isUnique: true)
);

The package integrates seamlessly with EF Core's design-time tooling, requiring zero additional ceremony—just configure and migrate.