Bug #12244 | ResultSet.getLong returns a incorrect value | ||
---|---|---|---|
Submitted: | 28 Jul 2005 18:28 | Modified: | 29 Jul 2005 12:14 |
Reporter: | Keita Kitamura | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | Connector / J | Severity: | S2 (Serious) |
Version: | 3.1.9, 3.1.10 | OS: | Any (any) |
Assigned to: | CPU Architecture: | Any |
[28 Jul 2005 18:28]
Keita Kitamura
[29 Jul 2005 7:19]
Vasily Kishkin
I was not able reproduce the bug: 1(getLong): 100 1(getInt): 100 --- 2(getLong): -2147483648 2(getInt): -2147483648 --- 3(getLong): -1 3(getInt): -1 --- I tested on 3.1.10. What version of mysqld did you use ?
[29 Jul 2005 9:17]
Keita Kitamura
I'm using 4.1.10a installed by rpm on WBEL4. By the way, your output was wrong too, right? Since INTEGER UNSIGNED supports 0 to 4294967295, 2(getLong) is expected to be 2147483648 and 3(getLong) should be 4294967295, aren't they?
[29 Jul 2005 9:51]
Vasily Kishkin
Ah...sorry...you are right.
[29 Jul 2005 12:14]
Mark Matthews
Dupe of a bug already fixed for 3.1.11, see http://downloads.mysql.com/snapshots.php#connector-j for a nightly snapshot build with the fix.