0

In databases for store prices shouldn't use float type (should be decimal). So is in JavaScript parseFloat() safe for prices?

For example I have array with 1000000 numbers and I would like parse all to float and do various operations throughout the set and in the whole.

Alex K.
  • 171,639
  • 30
  • 264
  • 288
jodohutu
  • 31
  • 3
  • 3
    Floats are floats so the same caveats apply, in JavaScript 0.1+0.2 is not 0.3. As 10 + 20 is 30 its best not to deal with fractional currencies at all and use whole integer small currency units. – Alex K. Aug 02 '17 at 10:48

1 Answers1

1

It depends on what you mean by "safe", but in general you shouldn't use floating-point math for prices. parseFloat only guarantees that the resulting floating-point number is the nearest IEEE double according to "round to nearest, ties to even" rounding mode. In most cases, this will result in a small rounding error:

> parseFloat("0.11").toFixed(40)
< "0.1100000000000000005551115123125782702118"

Further mathematical operations will increase the rounding error. If you make sure to round the final result to two decimal places with toFixed(2), you should get the expected result in most cases. But this isn't guaranteed:

> parseFloat("1.37") * 90 * 90 * 90 * 90 * 90 * 90 * 90 * 90
< 5897400777000001

Unless you really know what you're doing, work with integer values of the smallest currency unit to be on the safe side. Note that JavaScript's number type can only store integers up to 253 exactly.

nwellnhof
  • 32,319
  • 7
  • 89
  • 113