At 07:15:19, the low_24h for BTCUSDT in this one is 67568.0. When entering it in the table, I almost treated it as an integer and put it in the integer column. That decimal place at the end came straight from the API; I didn’t add it. In the same block, last 67980.01 and high_24h 71514.01 both have two decimal places, while BTC’s usd in prices, 67951, is clean, with no decimal point, and BSC’s tvl_usd in chain_tvl, 4769586638.971461, is a whole string of digits.
If you identify types just by how the numbers look, these rows would end up split across three places. I later switched to identifying them by field name: low_24h, last, and high_24h go in the ticker’s floating-point columns; usd stays exactly as the API provides it; and tvl_usd gets its own cell. None of them follows another’s formatting.
Also, BSC’s prev_tvl_usd is 5037071786, an integer, in the same row as the long decimal for the current value. These are just my personal records of the figures, not investment advice. Inconsistent formatting isn’t an error; the fields simply come from different sources.