Hi, Kristian, On Sep 11, Kristian Nielsen wrote: > Kristian Nielsen via developers <developers@lists.mariadb.org> writes: > > > If you want to give a warning for these functions, then you need to > > create an SQL mode or some other handle for the DBA to disable the > > warning and keep their application running. And the warning should > > explain why it's there, > > Ah, we have --old-mode for this purpose.
old mode isn't quite for that. it's to revert the new behavior *temporarily* to give users time to adjust their applications. so by the very definition every old-mode value is deprecated from the day it was introduced. Adding a deprecated option to disable a deprecated warning elsewhere sounds rather strange :) > So add a new mode for --old-mode that disables the warning for the > ENCODE/DECODE functions. And later that mode could re-enable the > functions, if you want to disable them by default after deprecation > period. technically, yes, we can add an old mode in 2028, when ENCODE/DECODE supposedly would be removed (if nothing will change during that time). An old mode to preserve ENCODE/DECODE for another five years. Regards, Sergei VP of MariaDB Server Engineering and secur...@mariadb.org _______________________________________________ developers mailing list -- developers@lists.mariadb.org To unsubscribe send an email to developers-le...@lists.mariadb.org
