Discussion of open issues, suggestions and bugs regarding Entity Developer - ORM modeling and code generation tool
- Posts: 68
- Joined: Tue 28 Apr 2009 10:11
I just want to ask if it is convenient to map TINYINT (in Mysql) to System.Byte by default.
TINYINT can contain negative vaules and Byte is usigned in C# (0-255). So, the following exception is raised in such cases:
Code: Select all
MESSAGE: Value was either too large or too small for an unsigned byte.
STACKTRACE: at System.Byte.Parse(String s, NumberStyles style, NumberFormatInfo info)
at Devart.Common.ap.ar(Byte A_0, Int32 A_1, Int32 A_2)
at lambda_method(ExecutionScope , b )
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
Thank you for the request, we've changed the default mapping for signed TinyInt to System.SByte. We will post here when the build with this change is available.
- Posts: 45
- Joined: Thu 20 Jan 2011 10:12
Hi there, it seems that this error is back in dotConnect for MySQL Pro v. 6.30.165 - I am getting this error with records having Tinyint = -1.