Invalid datatype: NUMERIC

Discussion of open issues, suggestions and bugs regarding LinqConnect – Devart's LINQ to SQL compatible ORM
Post Reply
listonic
Posts: 39
Joined: Mon 06 Dec 2010 15:47

Invalid datatype: NUMERIC

Post by listonic » Mon 28 Feb 2011 17:18

I am using SQL server, i have a field of type : numeric(18, 0).

I am using
Devart.Data.SqlServer.Linq ver 2.0.10.0



On select i receive an exception :

Invalid datatype: NUMERIC

Entity developer correctly recognizes the datatype numeric and translates it to decimal value.

This is a very urgent issue. Can i have a quick response how to fix it ?


Stack trace :

at Devart.Data.SqlServer.Linq.Provider.a.a(String A_0, Boolean A_1)
at Devart.Data.SqlServer.Linq.Provider.c.a.a(String A_0)
at Devart.Data.Linq.Provider.DataSourceInfo.TypeSystemProvider.GetProviderType(String typeName)
at Devart.Data.Linq.Provider.Query.SqlFactory.Default(MetaDataMember member)
at Devart.Data.Linq.Provider.Query.SqlFactory.Member(SqlExpression expr, MetaDataMember member)
at Devart.Data.Linq.Provider.Query.ag.a(SqlExpression A_0, MetaType A_1, List`1& A_2, List`1& A_3, SqlExpression& A_4, IList`1 A_5)
at Devart.Data.Linq.Provider.Query.ag.b(SqlExpression A_0, MetaType A_1, List`1& A_2, List`1& A_3, SqlExpression& A_4, IList`1 A_5)
at Devart.Data.Linq.Provider.Query.ag.a(x A_0, IList`1 A_1)
at Devart.Data.Linq.Provider.Query.ag.a(MetaType A_0, ITable A_1, IList`1 A_2)
at Devart.Data.Linq.Provider.Query.w.a(ITable A_0)
at Devart.Data.Linq.Provider.Query.w.j(Expression A_0)
at Devart.Data.Linq.Provider.Query.w.a(Expression A_0)
at Devart.Data.Linq.Provider.Query.w.a(Expression A_0, Expression A_1, LambdaExpression A_2, LambdaExpression A_3, LambdaExpression A_4)
at Devart.Data.Linq.Provider.Query.w.b(MethodCallExpression A_0)
at Devart.Data.Linq.Provider.Query.w.j(Expression A_0)
at Devart.Data.Linq.Provider.Query.w.a(Expression A_0, LambdaExpression A_1)
at Devart.Data.Linq.Provider.Query.w.b(MethodCallExpression A_0)
at Devart.Data.Linq.Provider.Query.w.j(Expression A_0)
at Devart.Data.Linq.Provider.Query.w.d(Expression A_0, Expression A_1)
at Devart.Data.Linq.Provider.Query.w.b(MethodCallExpression A_0)
at Devart.Data.Linq.Provider.Query.w.j(Expression A_0)
at Devart.Data.Linq.Provider.Query.w.a(Expression A_0)
at Devart.Data.Linq.Provider.Query.w.e(Expression A_0)
at Devart.Data.Linq.Provider.Query.w.b(MethodCallExpression A_0)
at Devart.Data.Linq.Provider.Query.w.j(Expression A_0)
at Devart.Data.Linq.Provider.Query.w.i(Expression A_0)
at Devart.Data.Linq.Provider.DataProvider.BuildQuery(Expression query)
at Devart.Data.Linq.Provider.DataProvider.Devart.Data.Linq.Provider.IProvider.Compile(Expression query)
at Devart.Data.Linq.DataQuery`1.i()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at UniItemsDs.GetAllActiveWithActiveItems() in UniItemsDs.cs:line 161

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

Post by StanislavK » Mon 28 Feb 2011 17:57

This is a known problem of the 2.20.10 version. It was fixed in the next build; please try updating to the latest 2.20.14 build of LinqConnect, and tell us if the problem persists.

The latest build can be downloaded from
http://www.devart.com/linqconnect/download.html
(the trial and free versions) or from Registered Users' Area (for users with active subscription only):
http://secure.devart.com/

Post Reply