Calculated field
MAX([amount])
Sample data
| id | amount | units | score | other |
|---|---|---|---|---|
| 1 | -2.5 | 2 | -0.8 | 3 |
| 2 | 0 | 0 | 0 | 4 |
| 3 | 1.5 | 3 | 0.25 | 2 |
| 4 | 4 | 4 | 0.5 | 8 |
| 5 | 9 | 5 | 0.8 | 11 |
| 6 | 16 | 6 | 1 | 14 |
| 7 | null | 7 | null | 9 |
| 8 | 4 | 8 | -0.5 | null |
The same calculation as SQL
SELECT max(amount) AS result FROM input
Runs the example above.
SELECT max(amount) AS result FROM input
Written for this dialect; not run here.
SELECT max(amount) AS result FROM input
Written for this dialect; not run here.
Result
| result |
|---|
| 16 |
Same rows from the calculation and from the SQL in DuckDB.
Where a naive translation goes wrong
- Filtering out zero and negative observations can change the aggregate.
Naive SQL
SELECT max(amount) FILTER (WHERE amount<10) AS result FROM input
result 9 Matches the calculation
SELECT max(amount) AS result FROM input
result 16
Signature
MAX(expression, [expression])