Closed woolfg closed 1 year ago
NEWDECIMAL
is handeled as string as the decimal is not the same as float. we could cast it to float by applying CAST("3.5" as FLOAT)
. although this is not the same as we lose precision. this is not a problem for us at the moment but I would argue the handling is correct and the client of the api can decide how to store/handle the precision. so I would vouch for not chaning it.
fyi @mre
calculated string are decimal, so it seems to be a problem in the js code while converting