Bug #88227 | Connector/J 5.1.44 cannot be used against MySQL 5.7.20 without warnings | ||
---|---|---|---|
Submitted: | 25 Oct 2017 17:22 | Modified: | 17 Feb 2018 2:50 |
Reporter: | Francisco Lozano | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / J | Severity: | S2 (Serious) |
Version: | OS: | Any | |
Assigned to: | Filipe Silva | CPU Architecture: | Any |
[25 Oct 2017 17:22]
Francisco Lozano
[26 Oct 2017 13:27]
Chiranjeevi Battula
Hello Francisco, Thank you for the bug report. Verified based on internal discussion with dev's. Thanks, Chiranjeevi.
[22 Nov 2017 10:36]
Francisco Lozano
Given that this is confirmed and that this renders latest MySQL unusable from Java... when do you plan to fix?
[17 Feb 2018 2:50]
Daniel So
Posted by developer: Added the following entry to the Connector/J 5.1.46 changelog: "When Connector/J 5.1.44 or earlier connected to MySQL 5.7.20 or later, warnings are issued because Connector/J used the deprecated system variables tx_isolation and tx_read_only. These SQL-level warnings, returned from a SHOW WARNINGS statement, might cause some applications to throw errors and stop working. With this fix, the deprecated variables are no longer used with MySQL 5.7.20 and later; also, to avoid similar issues, a SHOW WARNINGS statement is no longer issued for the use of deprecated variables."