Bug #88070 | Too limited compatibility options for transaction isolation | ||
---|---|---|---|
Submitted: | 12 Oct 2017 7:17 | Modified: | 16 Oct 2017 11:58 |
Reporter: | Daniël van Eeden (OCA) | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Options | Severity: | S3 (Non-critical) |
Version: | 8.0.3 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | compatibility, transaction_isolation, tx_isolation |
[12 Oct 2017 7:17]
Daniël van Eeden
[16 Oct 2017 5:36]
Simon Mudd
Bottom line: deprecation of old functionality should be done with more care and giving people and code "time to migrate". I was one of the people to request that variable names are consistent but this change is too quick and clearly not thought out and there seems to be little consideration of people who run multiple major MySQL versions at once.
[16 Oct 2017 11:58]
MySQL Verification Team
Hello Daniël, Simon, Thank you for the report and feedback! Regards, Umesh