![](https://secure.gravatar.com/avatar/359652f5d5394fdc76fea714c0e40c97.jpg?s=120&d=mm&r=g)
mariadb-10.3.36 versus mariadb-10.3.37 in the past every field contained "collate latin1_german1_ci" and after this point-update collation is only part of the output if it's different then the tables default collation surely, i can update everything to mariadb-10.3.37 and rewrite all this tests in the hope the next point-update don't restore the old behavior but it's really a bad style --------------------------------------------------------------------------------------------------------------------- CALLER: '/autotests/custom/phpincludes_mysql.php:306': --------------------------------------------------------------------------------------------------------------------- --- old_9bb3995c3244abfff522da086526e88b5a8a81f1e7cf672d8343f20d.txt 2022-11-10 01:03:12.366665303 +0100 +++ new_53033703b16454931e7c7f62ef923229ca8183aff6f6fa017cdb44bd.txt 2022-11-10 01:03:12.366665303 +0100 @@ -1,14 +1,14 @@ create table `test_table` (`test_id` mediumint(7) unsigned not null auto_increment, -`char_char` char(200) collate latin1_german1_ci default null, +`char_char` char(200) default null, `char_date` date default null, `char_datetime` datetime default null, -`char_longtext` longtext collate latin1_german1_ci default null, -`char_mediumtext` mediumtext collate latin1_german1_ci default null, -`char_text` text collate latin1_german1_ci default null, +`char_longtext` longtext default null, +`char_mediumtext` mediumtext default null, +`char_text` text default null, `char_time` time default null, `char_timestamp` datetime default null, -`char_tinytext` tinytext collate latin1_german1_ci default null, -`char_varchar` varchar(200) collate latin1_german1_ci default null, +`char_tinytext` tinytext default null, +`char_varchar` varchar(200) default null, `number_bigint` bigint(200) unsigned default null, `number_double` double unsigned default null, `number_float` double unsigned default null,