Jonathan Amend

I found you can avoid the `transform: translateY(...)` from being applied on scroll if you set `excessRows: Number.MAX_VALUE` in the grid options.

I think I've run into the same issue. Here is a more concise example to reproduce it: EntityFramework6.Npgsql 6.4.0 Npgsql 4.1.2 PostgreSQL 10.6 For context, I'm also upgrading from Npgsql...

These commits seem suspicious: https://github.com/npgsql/npgsql/commit/94d99fad7c4bdbdfbf32fea85d0ef6ede15801b5 https://github.com/npgsql/npgsql/commit/26acce17147fe9f9367c17b2675a118601348f4e Specifically, the handling of PrimitiveTypeKind.String and DbType.String as NpgsqlDbType.Unknown. Trying with 3.0.1, I get these parameters and it works: p__linq__0: 'X' (Type = String)...

I took varchar from the fix for the similar issue #27 as an example: https://github.com/npgsql/EntityFramework6.Npgsql/commit/e1689b94b8b83e94023f5bfb751b6345349d550c#diff-e299df15cc3fa1e8f0a2b9ea9fa5ac80

I ran into this issue in 9.0. To reproduce it, make `Linked.Diff` nullable and don't assign it a value. Workaround: `NextMonth = x.Linked.Diff == null ? null : x.Date.Value.AddDays(x.Linked.Diff)`

@roji In reproducing the issue I realized my use case is a bit different from the original (`DateTime` instead of `DateOnly`), so perhaps it has since been fixed for `DateOnly`,...

I was also able to reproduce it with `DateOnly` with a test case in `GearsOfWarQueryNpgsqlTest`: ``` [ConditionalTheory] [MemberData(nameof(IsAsyncData))] public virtual async Task Select_DateOnly_NullProjection_AddYears(bool async) { await AssertQuery( async, ss =>...