Skip/Take parameter types misconfigured

Hi. I’m trying to make EF Core work with pg_trgm extension. Here is stripped down sample application to demonstrate issue https://github.com/osovitskiy/npgsql-efcore-sample While simple query like

context.Parent.Where(x => x.Name.FuzzyMatches("foobar")).ToList();

executes fine, more complex query with pagination

var entities = 
    context.Entities
           .Where(x => 
               context.Entities
                      .Where(y => y.Name.FuzzyMatches(search))
                      .OrderBy(y => y.Name.WordSimilarity(search))
                      .Skip(skip)
                      .Take(take)
                      .Select(y => y.Id)
                      .Contains(x.Id))
           .OrderBy(x => x.Name.WordSimilarity(search))
           .ToList();

translates correctly

SELECT x."Id", x."Name"
FROM "Entities" AS x
WHERE x."Id" IN (
    SELECT y."Id"
    FROM "Entities" AS y
    WHERE (y."Name" %> @__search_0) = TRUE
    ORDER BY (y."Name" <->> @__search_0)
    LIMIT @__take_2 OFFSET @__skip_1
)
ORDER BY (x."Name" <->> @__search_0)

but fails to execute with error System.InvalidCastException: Can't write CLR type System.String with handler type Int32Handler because it tries to write @__search_0 parameter as Int32.

Same expression works fine if I replace FuzzyMatches call with any of string.Contains / EF.Functions.Like / EF.Functions.ToTsVector().Matches(). Any suggestions?

[roji]

Let’s revisit it after we port to preview7. So much is changing there that the problem may go away (or its resolution may be very different).

[roji]

Revisiting this after a long time, and @austindrenski’s simplified repo works fine on EF Core 3.1. Many type mapping inference issues were fixed in 3.0, so it would make sense this works now.

If there’s still an issue here, please post back and I’ll revisit.