Anonymous - 2021-10-05

Same problem here, and it arises also when updating INTEGER values, probably because the produced SQL contains a number formatted as a FLOAT.