Type mapping error

Discussion of open issues, suggestions and bugs regarding LinqConnect – Devart's LINQ to SQL compatible ORM
Post Reply
larsholm
Posts: 1
Joined: Tue 01 Mar 2011 21:03

Type mapping error

Post by larsholm » Tue 01 Mar 2011 21:13

TimeSpan is mapped to bigint in SQL Server. And the SQL Server type time is mapped to Object.

StanislavK
Devart Team
Posts: 1710
Joined: Thu 03 Dec 2009 10:48

Post by StanislavK » Wed 02 Mar 2011 12:39

Thank you for the report, we will analyze this issue and inform you about the results as soon as possible.

StanislavK
Devart Team
Posts: 1710
Joined: Thu 03 Dec 2009 10:48

Post by StanislavK » Fri 11 Mar 2011 18:02

We have fixed this issue: now System.TimeSpan is mapped to 'Time' and vice versa. This fix is available in the new 2.20.15 build of LinqConnect. The new build can be downloaded from
http://www.devart.com/linqconnect/download.html
(the trial version) or from Registered Users' Area (for users with active subscription only):
http://secure.devart.com/

For the detailed information about the fixes and improvements available in LinqConnect 2.20.15, please refer to
http://www.devart.com/forums/viewtopic.php?t=20478

Post Reply