Bug #49794 | MySqlDataReader.GetUInt64 doesn't work for large BIGINT UNSIGNED | ||
---|---|---|---|
Submitted: | 18 Dec 2009 3:46 | Modified: | 15 Jan 2010 10:34 |
Reporter: | Marcus Lo | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / NET | Severity: | S2 (Serious) |
Version: | 6.1.3 | OS: | Windows |
Assigned to: | Tony Bedford | CPU Architecture: | Any |
[18 Dec 2009 3:46]
Marcus Lo
[8 Jan 2010 23:03]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/96456 782 Reggie Burnett 2010-01-08 - fixed a bug with prepared statements and unsigned bigint. Patch also provided a nice speedup to reading integer values from the wire (bug #49794)
[8 Jan 2010 23:07]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/96459 799 Reggie Burnett 2010-01-08 [merge] fixed a bug with prepared statements and unsigned bigint. Patch also provided a nice speedup to reading integer values from the wire (bug #49794)
[8 Jan 2010 23:12]
Reggie Burnett
fixed in 6.0.6, 6.1.4, and 6.2.3
[15 Jan 2010 10:34]
Tony Bedford
An entry has been added to the 6.0.6, 6.1.4, 6.2.3 changelogs: MySqlDataReader.GetUInt64 returned an incorrect value when reading a BIGINT UNSIGNED column containing a value greater than 2147483647