Bug #15098 | CAST(column double TO signed int), wrong result | ||
---|---|---|---|
Submitted: | 21 Nov 2005 13:17 | Modified: | 4 Apr 2006 13:52 |
Reporter: | Matthias Leich | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 4.1 | OS: | |
Assigned to: | Alexander Barkov | CPU Architecture: | Any |
[21 Nov 2005 13:17]
Matthias Leich
[21 Nov 2005 13:19]
Matthias Leich
test case
Attachment: ml002.test (application/test, text), 561 bytes.
[21 Nov 2005 13:19]
Matthias Leich
my test result
Attachment: ml002.reject (application/octet-stream, text), 800 bytes.
[6 Dec 2005 12:57]
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/internals/33070
[28 Mar 2006 12:14]
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/4231
[29 Mar 2006 14:38]
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/4278
[31 Mar 2006 16:40]
Alexander Barkov
Fixed in 4.1.19, 5.0.21, 5.1.9
[4 Apr 2006 13:52]
Paul DuBois
Noted in 4.1.19, 5.0.21, 5.1.9 changelogs. <literal>CAST<replaceable>double</replaceable> AS SIGNED INT)</literal> for large <replaceable>double</replaceable> values outside the signed integer range truncates the result to be within range, but the result sometimes had the wrong sign, and no warning was generated. (Bug #15098) (a warning occurs only in 5.0 and up)