Calculated field
LEFT([label], 4)
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 left(label,4) AS result FROM input
Runs the example above.
SELECT left(label,4) AS result FROM input
Written for this dialect; not run here.
SELECT left(label,4) AS result FROM input
Written for this dialect; not run here.
Result
| result |
|---|
| ce |
| ORCH |
| mapl |
| will |
| birc |
| pine |
| ash |
| null |
Same rows from the calculation and from the SQL in DuckDB.
Where a naive translation goes wrong
- Replacing LEFT with right(label,4) changes the shown values or null handling.
Naive SQL
SELECT right(label,4) AS result FROM input
result ar west east orth irch outh ash null Matches the calculation
SELECT left(label,4) AS result FROM input
result ce ORCH mapl will birc pine ash null
Signature
LEFT(string, count)