Op ma 28 jan. 2019 om 12:33 schreef Marko Mäkelä <[email protected]>: > there would be no issue when upgrading. Would it be thinkable to add > the loose_ prefix to unknown options in configuration files? Or to
We can't rewrite history. > ship a new version of the default configuration file, commenting out > the old (now redundant) settings? Then those users who modified the > configuration files would be alerted about the problem when upgrading > the package. > The parameters innodb_large_prefix and innodb_file_format were > deprecated in MySQL 5.7 and MariaDB 10.2, and removed in MySQL 8.0 and > MariaDB 10.3. What's the deprecation policy? I think the time between deprecation and removal is too short. > How long should obscure parameters be preserved? Were large-prefix and file-format obscure? They were in the debian default maria db conf files.. How long? Ideally until major distros have all shipped a MariaDB version with the deprecation warnings. Treating unknown settings as warnings rather then errors would work too. > Forever? What about > old syntax? The following worked in MySQL 5.0, but no longer in MySQL > 5.1 or MariaDB: > create table t(a int) type=innodb; Syntax is different, when did engine= become available? -- Olaf
