Closed enterpub closed 1 year ago
P. S. I do not think the issue is in Dapper library itself, because I used Dapper 2.0.35 with Dommel 1.11.0 before for many months and had no issues. That is why I think something changed in Dommel
That's strange. Does using DateTime
as the type for RowVersion
works? That does work for MySQL but it seems that you're using SQL Server.
Hi, I use SqlServer as you mentioned
Microsoft SQL Server 2016 (SP1-GDR) (KB4505219) - 13.0.4259.0 (X64)
Jun 15 2019 19:20:12
Developer Edition (64-bit) on Windows 10 Pro 6.3
I did not try DateTime
, but I will and let you know.
The .net equivalent for sql server timestamp
is byte[]
. Event if DateTime
works it would still be confusing to use it
Did you try to use TimeSpan
or TimeSpan?
?
@lucasloss, the mapping type for timestamp
in .net is byte[]
. I should not map it to TimeSpan
even if it would work.
timestamp
has no common with time or date. It is just a confusing name of the sql sever type.
SQL Server Data Type Mappings
@enterpub are you still facing this issue? Could be a Dapper issue? I don't see how Dommel this is related to Dommel.
Hi @henkmollema, I'll test it when have a chance. We are still using version 1.11.0 because of that issue.
Closing this for now.
.NET Core 3.1 Win 10 64 bit Dommel 2.1.0 Dapper 2.0.35
Hi, after upgrading to Dommel 2.1.0 from 1.11.0 I can not retrieve any entity if it has column of
timestamp
type in database. For example, there is a table in database:I have a related class:
Whenever I try to retrieve the
ChargeDb
instance it throws an exception:If I delete the
RowVersion
property It works as expected. Means do this:Could you take a look? Please, ask any questions, I'll respond quickly