DateOnly "off by one" column error about dapper

[mgravell]

Well that sounds very bad; I'm hiding 2.1.44 while I investigate - hopefully should have a fix out today or tomorrow

[mgravell]

well, I'm going to assume it isn't as exotic as that and is simply a "Marc is an idiot" thing; hopefully should be able to look on Friday (I've been completely snowed under)

[quiian]

Also ran into this, dapper attempts to parse DateOnly from column 11 instead of column 12. Code was working fine before we updated. Attempting to roll back for now.. :)

[sander1095]

I'm running into the same issue. I stronly feel that it is related #2051 as I had my own SqlMapper.TypeHandler<DateOnly> . I feel like Dapper now ignores my custom handler and uses it's built-in one.

Perhaps it's also worth talking about that specific behaviour. Wouldn't it make more sense for Dapper to still use my own mapper, which (probably) should not have made this bug show up in my code?

[Gondlir]

I had almost the same problem. Tell me, do you use .NET 8 with Arm64?
Where I work there is a team that uses Dapper. They upgraded to .NET 8 with ARM64 and had problems parsing columns.
I'm not sure if this was 100% the cause but I had the same problem in a project that used dapper, after this update to .NET 8 with ARM64 the Dapper simply broke.
I think it's worth the investigation @mgravell

[GonzaloVisma]

This is the same issue I reported in #2071

[mgravell]

I have been unable to get a repro of this failing; for now I guess I have no choice except to revert that change, but if anyone who was seeing this problem could show a runnable repro against 2.1.44 (or similar affected), I'd be very grateful

[Dean-NC]

I use 2.1.37 targeting .NET 8 with no problem for DateOnly for both records and classes. I use Microsoft.Data.SqlClient 5.1.3 (accepting the security risks and will stay on it until they split-out the basic client from Azure and Identity, mainly so it doesn't require .NET framework). I don't use any custom type mapping, and I use queries like:

connection.QueryAsync<MyRecord>("Select Id, Col2, MyDateCol From Table...")

So, I'll stay on .37. I also use Dapper.AOT, but it doesn't support DateOnly yet.

[Dean-NC]

If the db column is defined with a time component like DateTime2 or DateTime, then I do get this error of being off by 1, but not if the column is defined as Date.