Calculated field
FLOAT([quantity])
Sample data
| label | quantity | amount | flag |
|---|---|---|---|
| cedar cedar | 65 | 12.8 | True |
| ORCHID-west | 66 | -7.6 | False |
| maple-east | 67 | 0 | null |
| willow north | 68 | 25.3 | True |
| birch-birch | 69 | 4.9 | False |
| pine/south | 70 | -1.2 | null |
| ash | 71 | 9 | True |
| null | null | null | null |
The same calculation as SQL
SELECT quantity::double AS result FROM input
Runs the example above.
SELECT CAST(quantity AS DOUBLE) AS result FROM input
Written for this dialect; not run here.
SELECT CAST(quantity AS FLOAT64) AS result FROM input
Written for this dialect; not run here.
Result
| result |
|---|
| 65 |
| 66 |
| 67 |
| 68 |
| 69 |
| 70 |
| 71 |
| null |
Same rows from the calculation and from the SQL in DuckDB.
Where a naive translation goes wrong
- Replacing FLOAT with quantity::varchar changes the shown values or null handling.
Naive SQL
SELECT quantity::varchar AS result FROM input
result 65 66 67 68 69 70 71 null Matches the calculation
SELECT quantity::double AS result FROM input
result 65 66 67 68 69 70 71 null
Signature
FLOAT(expression)