Bug #5874 | Timezone conversion goes in the wrong direction | ||
---|---|---|---|
Submitted: | 4 Oct 2004 9:19 | Modified: | 23 Nov 2004 18:18 |
Reporter: | Philip Ross | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | Connector / J | Severity: | S2 (Serious) |
Version: | 3.0.15-ga, 3.1.4-beta | OS: | Windows (Windows XP) |
Assigned to: | Eric Herman | CPU Architecture: | Any |
[4 Oct 2004 9:19]
Philip Ross
[23 Nov 2004 18:18]
Mark Matthews
As far as I we can tell, this isn't a bug, because it's consistent with what the JDBC spec requires, and with what other vendors do (the '+=' offset bit actually comes from another bug report, where we go in this direction to be JDBC compliant and like other vendors, see http://bugs.mysql.com/bug.php?id=3620) If your case doesn't match BUG#3620 (please look at the entire thread, and determine if you agree or disagree with it's conclusion), or if you believe this conclusion to be in error, please re-open this bug.
[26 Nov 2004 16:34]
Eric Herman
Another quick note, when retrieving Timestamp values, it is usually best to use ResultSet's "getTimestamp" method: ResultSet rs = this.stmt.executeQuery("SELECT * from tableBug5874"); while (this.rs.next()) { // correct: Timestamp retrTimestamp = this.rs.getTimestamp(1); // usually incorrect: String retrTimestampString = this.rs.getString(1);