Calculated field
SPLIT([label], '-', -1)
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 split_part(label,'-',-1) AS result FROM input
Runs the example above.
SELECT split_part(label,'-',-1) AS result FROM input
Written for this dialect; not run here.
SELECT ARRAY_REVERSE(SPLIT(label,'-'))[SAFE_OFFSET(0)] AS result FROM input
Written for this dialect; not run here.
Result
| result |
|---|
| cedar cedar |
| west |
| east |
| willow north |
| birch |
| pine/south |
| ash |
| null |
Same rows from the calculation and from the SQL in DuckDB.
Where a naive translation goes wrong
- Replacing SPLIT with split_part(label,'-',1) changes the shown values or null handling.
Naive SQL
SELECT split_part(label,'-',1) AS result FROM input
result cedar cedar ORCHID maple willow north birch pine/south ash null Matches the calculation
SELECT split_part(label,'-',-1) AS result FROM input
result cedar cedar west east willow north birch pine/south ash null
Signature
SPLIT(string, string, expression)