Unsiged Big Int Mapped To Decimal

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for MySQL
Post Reply
remonlucassen
Posts: 3
Joined: Tue 21 Jun 2016 19:51

Unsiged Big Int Mapped To Decimal

Post by remonlucassen » Tue 21 Jun 2016 20:03

Hi,

Why is a MYSQL Unsigned Big Int which should be unsigned 64 bit integer mapped to a .NET Decimal (128 Bits) instead of a .NET Unsigned Long (UINT64) which indicates it's the same datatype.

I have to use a type converter to go from MySQL 64Bit Unsigned integer to a .NET 64 Bit Unsigned Integer.

It makes no sense to me

Can you explain ?

Shalex
Site Admin
Posts: 8245
Joined: Thu 14 Aug 2008 12:44

Re: Unsiged Big Int Mapped To Decimal

Post by Shalex » Wed 22 Jun 2016 07:54

1. Are you using a plain ADO.NET (MySqlDataReader / MySqlDataTable) or an ORM framework (Entity Framework / NHibernate / LinqConnect / Telerik)?
2. If it is ORM, what is your ORM designer (e.g.: Entity Developer)?

remonlucassen
Posts: 3
Joined: Tue 21 Jun 2016 19:51

Re: Unsiged Big Int Mapped To Decimal

Post by remonlucassen » Wed 22 Jun 2016 20:06


Shalex
Site Admin
Posts: 8245
Joined: Thu 14 Aug 2008 12:44

Re: Unsiged Big Int Mapped To Decimal

Post by Shalex » Mon 27 Jun 2016 18:06

There is no unsigned .NET data types support in EF1 / EF4 / EF5 / EF6.

In case of plain ADO.NET, the usage of unsigned data types is avoided to make code be CLS compliant.

remonlucassen
Posts: 3
Joined: Tue 21 Jun 2016 19:51

Re: Unsiged Big Int Mapped To Decimal

Post by remonlucassen » Wed 29 Jun 2016 08:07

Ok

sounds reasonable thanx for clarifying.

Post Reply