Calculated field
INT([amount])
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 trunc(amount)::bigint AS result FROM input
Runs the example above.
SELECT CAST(TRUNC(amount) AS BIGINT) AS result FROM input
Written for this dialect; not run here.
SELECT CAST(TRUNC(amount) AS INT64) AS result FROM input
Written for this dialect; not run here.
Result
| result |
|---|
| 12 |
| -7 |
| 0 |
| 25 |
| 4 |
| -1 |
| 9 |
| null |
Same rows from the calculation and from the SQL in DuckDB.
Where a naive translation goes wrong
- Replacing INT with amount::bigint changes the shown values or null handling.
Naive SQL
SELECT amount::bigint AS result FROM input
result 13 -8 0 25 5 -1 9 null Matches the calculation
SELECT trunc(amount)::bigint AS result FROM input
result 12 -7 0 25 4 -1 9 null
Signature
INT(expression)