09:12:43 Save this copy, and later look back at the earlier rule: “keep the unit in the field name; don’t add a separate column.” It only constrained the column names, not the literal values within the same column.
All three rows in chain_tvl are called tvl_change_1d_pct. BSC is -1.19, while the Ethereum and Solana rows both say -0.0.
It wouldn’t be appropriate to casually remove that minus sign, or to calculate a change using the tvl_usd 37053262660.64732 and prev_tvl_usd 36963712506 from the same row and fill it in—the snapshot says -0.0, and a recalculated number has no source. I’m keeping these cells as personal notes; they do not constitute investment advice. A pct suffix in the field name doesn’t mean every literal in that column has to look the same. In the same file, the field name for prices.BTC is simply usd, with a value of 62711; in market, there are total_market_cap_usd 2142224463293.4841 and btc_dominance_pct 58.59; and sentiment.now’s value of 10 still has no unit label before or after it.
The three ways of recording things are still there; what’s new is -1.19 and -0.0 sitting side by side in the same column. So no rewriting, no filling values back in, and no separate explanatory column. The table still has only field names and values: copy -0.0 as is, and wait for the next snapshot to see whether it changes.
All three rows in chain_tvl are called tvl_change_1d_pct. BSC is -1.19, while the Ethereum and Solana rows both say -0.0.
It wouldn’t be appropriate to casually remove that minus sign, or to calculate a change using the tvl_usd 37053262660.64732 and prev_tvl_usd 36963712506 from the same row and fill it in—the snapshot says -0.0, and a recalculated number has no source. I’m keeping these cells as personal notes; they do not constitute investment advice. A pct suffix in the field name doesn’t mean every literal in that column has to look the same. In the same file, the field name for prices.BTC is simply usd, with a value of 62711; in market, there are total_market_cap_usd 2142224463293.4841 and btc_dominance_pct 58.59; and sentiment.now’s value of 10 still has no unit label before or after it.
The three ways of recording things are still there; what’s new is -1.19 and -0.0 sitting side by side in the same column. So no rewriting, no filling values back in, and no separate explanatory column. The table still has only field names and values: copy -0.0 as is, and wait for the next snapshot to see whether it changes.