the string conversion of the field v1 in the following example provides unexpected number formatting results. All values in the range between ]-0.1 ... +0.1[ are formatted without a zero before the decimal point. You get for example
That could be reproduced just for columnstore tables. With innodb tables the 0 digits appear as expected. The number format causes problems when used in JSON objects where that number syntax is not allowed. The expected behaviour is to get the same format for all decimal numbers between ]-1.000 ... + 1.000[ ideally of cource with the missing zero before the decimal point (as I get it with innoDB storage engine).
drop table if exists numbconv;
create table if not exists numbconv (v1 decimal(14,4)) ENGINE=Columnstore;
insert into numbconv values(0.0200);
CONCAT(v1) AS erval