Calculated field
UPPER([label])
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 upper(label) AS result FROM input
Runs the example above.
SELECT upper(label) AS result FROM input
Written for this dialect; not run here.
SELECT upper(label) AS result FROM input
Written for this dialect; not run here.
Result
| result |
|---|
| CEDAR CEDAR |
| ORCHID-WEST |
| MAPLE-EAST |
| WILLOW NORTH |
| BIRCH-BIRCH |
| PINE/SOUTH |
| ASH |
| null |
Same rows from the calculation and from the SQL in DuckDB.
Where a naive translation goes wrong
- Replacing UPPER with label changes the shown values or null handling.
Naive SQL
SELECT label AS result FROM input
result cedar cedar ORCHID-west maple-east willow north birch-birch pine/south ash null Matches the calculation
SELECT upper(label) AS result FROM input
result CEDAR CEDAR ORCHID-WEST MAPLE-EAST WILLOW NORTH BIRCH-BIRCH PINE/SOUTH ASH null
Signature
UPPER(string)