Why is the Date Written with One Day Offset via Connector/J
(Doc ID 2495188.1)
Last updated on MARCH 02, 2020
Applies to:MySQL Connectors - Version 8.0 and later
Information in this document applies to any platform.
Connector/J 5.1 Version
The timezone conversion is not tightly defined in the JDBC protocol, so it was originally handled by allowing the user to add the connection properties `noTimezoneConversionForDateType` and `noTimezoneConversionForDateType` so that users could choose what default behavior they prefer. With the 8.0 version designed to remove a lot of non-standard options and make it as clean as possible to the standard, these options have been removed. This leaves was some may consider a bug or inconsistent state in how dates are handled for timezones, but it does not violate the JDBC standard, so is not considered a bug.
Why are my dates out by one day and how do I fix it?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document