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 ?
Unsiged Big Int Mapped To Decimal
Re: Unsiged Big Int Mapped To Decimal
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)?
2. If it is ORM, what is your ORM designer (e.g.: Entity Developer)?
-
- Posts: 3
- Joined: Tue 21 Jun 2016 19:51
Re: Unsiged Big Int Mapped To Decimal
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.
In case of plain ADO.NET, the usage of unsigned data types is avoided to make code be CLS compliant.
-
- Posts: 3
- Joined: Tue 21 Jun 2016 19:51
Re: Unsiged Big Int Mapped To Decimal
Ok
sounds reasonable thanx for clarifying.
sounds reasonable thanx for clarifying.