MySQL Bugs: #92153: Time not converted into the JVM's time zone when useLegacyDatetimeCode=false

Bug #92153	Time not converted into the JVM's time zone when useLegacyDatetimeCode=false
Submitted:	23 Aug 2018 12:13	Modified:	28 Sep 2018 15:12
Reporter:	Andrey Shcheglov	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	Connector / J	Severity:	S3 (Non-critical)
Version:	5.1.46	OS:	Debian (Linux unit-725 4.9.0-5-amd64 #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04) x86_64 GNU/Linux)
Assigned to:	Filipe Silva	CPU Architecture:	x86 (x86_64)
Tags:	gettimestamp, settimestamp, time zone, timestamp, useLegacyDatetimeCode

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

The JUnit 4 test covering the scenarios described

Attachment: TimeZoneTest.java (text/x-java), 9.83 KiB.

Eclipse JUnit runner with test results

Attachment: eclipse-junit.png (image/png, text), 25.58 KiB.