7 ms·
Product Manager for the MySQL server here. w.r.t. tx_isolation: In MySQL 8.0, it is called transaction_isolation which is the name used by configuration files
by morgo 9y ago
Product Manager for the MySQL server here.
w.r.t. tx_isolation:
In MySQL 8.0, it is called transaction_isolation which is the name used by configuration files. MySQL 5.7 supports both names, but now warns when using the old name.
Supporting old+new names is required to support distributed apps which may upgrade a shard at a time (i.e. you want your code to work on both MySQL 5.7 and 8.0). But there is a deprecation warning to let you know which version is preferred.
Calling it an incompatible change is perhaps a little strong. The idea behind the deprecation warning is to give you as much notice as possible.
- pygy_ 9y ago> Calling it an incompatible change is perhaps a little strong. Definitions of backwards incompatibility are either tautological or disingenuous (provided we talk about documented behavior). The right way to do that change would have been to allow both names without warnings in a point/minor release (with the docs stating where the project is headed), add the depreciation warning with the next semver major one, and remove the old name on the next next semver major release.
- mattzito 9y agoThat though is a really long lifecycle for a product that may have a six month qualification and burn-in periods for a production enterprise implementation . You’re basically saying a change of config file parameter should take a year-plus?
- morgo 9y agoMySQL releases are 2-3 years. So it would be 4-6 years wait in this case :-)
- zzzeek 9y agoJust so you know, that warning broke Openstack builds in CI which fail for warnings like these. Other users have reported it elsewhere and I have users begging me to release SQLAlchemy 1.1.15 so that it can fix "the bug" ASAP for them. Unfortunately, "database suddenly emits a prominent, unconditional warning upon upgrade to 5.7.20" is a breaking change in many situations.
- morgo 9y agoWe are looking to add something to filter warnings in the future. Thx for the feedback.
- pygy_ 9y agoSorry for my unnecessarily harsh comment yesterday. A great course of action would be to put those deprecation warnings behind an opt-in flag. That would let curious people discover what they must change in order to migrate to future versions without breaking anything out of the box.