Query support for shadow properties on complex types

[AndriySvyryd]

[PascalVorwerk]

Hi, we are currently experiencing an issue with our complex property containing a class that evaluates to a string through a implicit operator. We are getting an error that linq doesn't know how to translate it.

If we change the configuration to OwnsOne configurations, it works fine.

Is this issue the issue we should be tracking for this error?

     builder.OwnsOne(c => c.CandidateDetails, owned =>
        {
            owned.OwnsOne(cd => cd.EmailAddress, b =>
            {
                b.Property(e => e.Value)
                    .HasColumnName("EmailAddress")
                    .HasMaxLength(100)
                    .IsRequired();
            });

            owned.Property(cd => cd.FirstName).HasColumnName("FirstName").HasMaxLength(100).IsRequired();
            owned.Property(cd => cd.LastName).HasColumnName("LastName").HasMaxLength(100).IsRequired();
            owned.Property(cd => cd.MiddleName).HasColumnName("MiddleName").HasMaxLength(100);
            owned.Property(cd => cd.CandidateNumber).HasColumnName("CandidateNumber").HasMaxLength(100);
        });

vs 

    public ComplexPropertyBuilder<CandidateDetails> Configure(ComplexPropertyBuilder<CandidateDetails> builder)
    {
        builder.Property(cd => cd.FirstName)
            .HasColumnName("FirstName")
            .HasMaxLength(100)
            .IsRequired();
        
        builder.Property(cd => cd.LastName)
            .HasColumnName("LastName")
            .HasMaxLength(100)
            .IsRequired();

        builder.Property(cd => cd.EmailAddress)
            .HasConversion(v => v.Value, v => new EmailAddress(v))
            .HasColumnName("EmailAddress")
            .HasMaxLength(100)
            .IsRequired();
        
        builder.Property(cd => cd.CandidateNumber)
            .HasColumnName("CandidateNumber")
            .HasMaxLength(100);

        builder.Property(cd => cd.MiddleName)
            .HasColumnName("MiddleName")
            .HasMaxLength(100);

        return builder;
    }


queryable = queryable.Where(x => x.CandidateDetails.LastName.Contains(query.Search) ||
                                             x.CandidateDetails.EmailAddress.Value.Contains(query.Search) ||
                                             x.CandidateDetails.FirstName.Contains(query.Search));

The first one works fine with the queryable described, but the 2nd one doesnt

[cincuranet]

@PascalVorwerk No. This issue is about shadow properties on complex types. Your mapping does not have shadow properties.

[roji]

Removing this from 10.0.0. The main point here was to support the existence discriminator for complex table splitting, which doesn't actually require full support for materializing shadow properties and was done in #36574.

Beyond that, full support of shadow properties is still tracked here, but is probably considerably less important.