Bug #61077 | unsigned BIGINT is mapped to decimal instead of unsigned long (Entity Framework) | ||
---|---|---|---|
Submitted: | 6 May 2011 8:20 | Modified: | 12 May 2011 15:55 |
Reporter: | Markus Wolters | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | Connector / NET | Severity: | S3 (Non-critical) |
Version: | 6.3.6 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | BIGINT, decimal, entity framework, UNSIGNED |
[6 May 2011 8:20]
Markus Wolters
[12 May 2011 15:55]
Reggie Burnett
Entity Framework doesn't support unsigned data types however MySQL does. So internally we have to map MySQL unsigned data type to the smallest signed EF data type that can contain the data. For an unsigned bigint, that it is a signed decimal type.
[20 Jun 2016 12:12]
Jianfeng Luo
The problem is unsigned Bigint is mapped to decimal, but decimal is NOT mapped back to unsigned bigint when we save the data. Caused so much agony.