Mapping arrays for properties (IReadOnlyCollection) with backing fields

Mapping arrays feature is really cool https://www.npgsql.org/efcore/mapping/array.html However when I work with DDD I would like to expose collections as readonly using IEnumerable or IReadOnlyCollection

public class Entity
{
    public IReadOnlyCollection<Guid> Attributes => attributes ;
    private Guid[] attributes = Array.Empty<Guid>();
}

and then, when I use LINQ on entity with backing field

.Where(c => c.Attributes.Contains(id))

it will generate in memory query instead of SQL query

WHERE "guid" = ANY("c"."Attributes")

Is it possible to support LINQ with sql properly for IReadOnlyCollection with backing fields?

[roji]

Perhaps that property reference in the fluent config should have been omitted?

Yeah, that’s what I meant - check out the docs on mapping fields without properties. The point is that EF Core doesn’t need to map - or even know - the property in question, it’s just a user-facing wrapper over the private field, which provides casting.

[YohDeadfall]

Regarding Collection, that again does not correspond well to the database type - PostgreSQL arrays are an ordered type, whereas a Collection isn’t. Mapping IList<T> to arrays does work though.

Checked that the new ordered dictionary class implements IList<T>. So other ordered collections should implement it as well, and there is no reason to support collection interfaces. But ArrayHandler lacks support of read only lists.