Bug #96383 | rs.getTimestamp() has different results for time fields with useCursorFetch=true | ||
---|---|---|---|
Submitted: | 31 Jul 2019 9:42 | Modified: | 7 Jan 2020 19:15 |
Reporter: | Slawomir Chodnicki | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / J | Severity: | S3 (Non-critical) |
Version: | 8.0.17 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[31 Jul 2019 9:42]
Slawomir Chodnicki
[31 Jul 2019 10:39]
MySQL Verification Team
Hello Slawomir, Thank you for the report. regards, Umesh
[7 Jan 2020 19:15]
Daniel So
Posted by developer: Added the following entry to the Connector/J 8.0.19 changelog: "When retrieving TIME values, using ResultSet.getTimestamp(), the fractional seconds are truncated when useCursorFetch=true. This patch corrects the problem by fixing the TIME value decoding in the MysqlBinaryValueDecoder. It also corrects some inconsistencies in formatting the fractional seconds when returning the TIME values as strings."