[MDEV-31811] deprecate old_mode values Created: 2023-07-31 Updated: 2023-10-01 Resolved: 2023-10-01 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Admin statements |
| Fix Version/s: | 11.3.1 |
| Type: | Task | Priority: | Critical |
| Reporter: | Sergei Golubchik | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | Preview_11.3 | ||
| Issue Links: |
|
||||
| Description |
|
old_mode was introduced as a temporary way to disable some of the new behavior, until the old applications are updated with it. It's not stored per SP and not replicated. This means every non-default value of old_mode is by design automatically deprecated. It should behave as such — setting it should issue a deprecation warning. And the usual deprecation rules (remove when all versions where it's not deprecated are EOLed) should apply. This task is about printing a deprecation warning when a old_mode is set to a non-default value. |
| Comments |
| Comment by Sergei Golubchik [ 2023-09-08 ] |
|
even though they were added (and thus deprecated) long ago, let's count the time from 11.3, the version when a warning was added. |
| Comment by Elena Stepanova [ 2023-09-18 ] |
|
It looks okay to me for 11.3.1 release. There may be more challenges when we start actually deleting values, but if so, it will be a separate issue. |