Design tidb_enable_strict_compatibility_80 = BOOLEAN #9141
Labels
feature/accepted
This feature request is accepted by product managers
priority/P2
The issue has P2 priority.
type/feature-request
Categorizes issue or PR as related to a new feature.
Milestone
Feature Request
Is your feature request related to a problem? Please describe:
In planning MySQL 8.0 compatibility, we would like to offer a smoother upgrade than MySQL 5.7 -> 8.0 offers.
For example:
set tx_isolation = x
is removed.GRANT
auto-creating users is removed (theNO_AUTO_CREATE_USER
sql mode is meaningless).Describe the feature you'd like:
I propose we create a new setting, roughly named
tidb_enable_strict_compatibility_80
, defaultFALSE
. This means by default there will be better compatibility with 5.7 where possible, but a user can opt-in to MySQL 8.0 behavior.This has the advantage of future smoother upgrades and sometimes improved usability, security etc. A future release may enable strict compatibility by default.
Describe alternatives you've considered:
It could also be possible to enable strict compatibility by default.
Teachability, Documentation, Adoption, Migration Strategy:
It will need some design to work out what conditions require compatibility. Trivial items like removing unused variables should not provide compatibility.
The text was updated successfully, but these errors were encountered: