Bug #91065 | zeroDateTimeBehavior=CONVERT_TO_NULL should not apply to 00:00:00 TIME columns | ||
---|---|---|---|
Submitted: | 29 May 2018 21:56 | Modified: | 14 Dec 2018 22:46 |
Reporter: | Josh Landin | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / J | Severity: | S2 (Serious) |
Version: | 8.0.11 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[29 May 2018 21:56]
Josh Landin
[30 May 2018 12:55]
Chiranjeevi Battula
Hello Josh Landin, Thank you for the bug report and testcase. Verified this behavior on MySQL Connector / J 8.0.11. Thanks, Chiranjeevi.
[2 Oct 2018 18:09]
Josh Landin
Any estimate on fix version/timing?
[3 Dec 2018 17:43]
vish ramkee
Guys, any plans on getting this fixed soon?
[14 Dec 2018 22:46]
Daniel So
Posted by developer: Added the following entry to the Connector/J 8.0.14 changelog: "When the connection property zeroDateTimeBehavior was set to CONVERT_TO_NULL, Connector/J converted a TIME type value of 00:00:00 to null. With this fix, it returns a java.sql.Time instance of zero hours, minutes, and seconds, as expected."