Calculated field
{ FIXED : SUM([Revenue]) }
Sample data
| Region | Team | Customer | Revenue | Seats | Date |
|---|---|---|---|---|---|
| North | Cedar | Aster | 120 | 4 | 2026-01-05 |
| North | Cedar | Aster | 80 | 2 | 2026-02-05 |
| North | Cedar | Birch | 300 | 6 | 2026-01-12 |
| North | Pine | Clover | 90 | 3 | 2026-02-14 |
| South | Elm | Dahlia | 200 | 5 | 2026-01-08 |
| South | Elm | Dahlia | 100 | 2 | 2026-02-08 |
| South | Ash | Fern | 75 | 3 | 2026-01-20 |
| South | Ash | Fern | 25 | 1 | 2026-02-20 |
The same calculation as SQL
SELECT SUM(Revenue) AS result FROM input WHERE Region='North'
Runs the example above.
SELECT SUM(Revenue) AS result FROM input WHERE Region='North'
Written for this dialect; not run here.
SELECT SUM(Revenue) AS result FROM input WHERE Region='North'
Written for this dialect; not run here.
Result
| result |
|---|
| 590 |
Same rows from the calculation and from the SQL in DuckDB.
Where a naive translation goes wrong
- Computing the fixed SUM before the context filter incorrectly includes South invoices.
Naive SQL
SELECT SUM(Revenue) AS result FROM input
result 990 Matches the calculation
SELECT SUM(Revenue) AS result FROM input WHERE Region='North'
result 590
Signature
{ FIXED : SUM([Revenue]) }