Calculated field
MAKETIME([hour],[minute],[second])
Sample data
| shipment | shipped | received | text | year | month | day | hour | minute | second | lat | lon | wkt |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 2024-12-29 | 2024-12-29T16:25:40 | 2024-12-29 | 2025 | 2 | 25 | 9 | 25 | 40 | 10 | 106 | POINT (106 10) |
| 2 | 2024-12-30 | 2024-12-30T16:25:40 | 2024-12-30 | 2025 | 2 | 26 | 10 | 25 | 40 | 10.1 | 106.1 | POINT (106.1 10.1) |
| 3 | 2025-01-01 | 2025-01-01T16:25:40 | 2025-01-01 | 2025 | 2 | 27 | 11 | 25 | 40 | 10.2 | 106.2 | POINT (106.2 10.2) |
| 4 | 2025-01-31 | 2025-01-31T16:25:40 | 2025-01-31 | 2025 | 2 | 28 | 12 | 25 | 40 | 10.3 | 106.3 | POINT (106.3 10.3) |
| 5 | 2025-02-28 | 2025-02-28T16:25:40 | 2025-02-28 | 2025 | 2 | 29 | 13 | 25 | 40 | 10.4 | 106.4 | POINT (106.4 10.4) |
| 6 | 2025-03-15 | 2025-03-15T16:25:40 | 2025-03-15 | 2025 | 2 | 30 | 14 | 25 | 40 | 10.5 | 106.5 | POINT (106.5 10.5) |
| 7 | null | null | null | 2025 | 2 | 31 | 15 | 25 | 40 | 10.6 | 106.6 | POINT (106.6 10.6) |
| 8 | 2024-02-29 | 2024-02-29T16:25:40 | 2024-02-29 | 2025 | 2 | 32 | 16 | 25 | 40 | 10.7 | 106.7 | POINT (106.7 10.7) |
The same calculation as SQL
SELECT TIMESTAMP '1899-12-30 00:00:00'+hour*INTERVAL '1 hour'+minute*INTERVAL '1 minute'+second*INTERVAL '1 second' AS result FROM input ORDER BY shipment
Runs the example above.
SELECT TIMESTAMP_NTZ_FROM_PARTS(DATE '1899-12-30',TIME_FROM_PARTS(hour,minute,second)) AS result FROM input ORDER BY shipment
Written for this dialect; not run here.
SELECT DATETIME(DATE '1899-12-30',TIME(hour,minute,second)) AS result FROM input ORDER BY shipment
Written for this dialect; not run here.
Result
| shipment | shipped | received | text | result |
|---|---|---|---|---|
| 1 | 2024-12-29 | 2024-12-29T16:25:40 | 2024-12-29 | 1899-12-30 09:25:40 |
| 2 | 2024-12-30 | 2024-12-30T16:25:40 | 2024-12-30 | 1899-12-30 10:25:40 |
| 3 | 2025-01-01 | 2025-01-01T16:25:40 | 2025-01-01 | 1899-12-30 11:25:40 |
| 4 | 2025-01-31 | 2025-01-31T16:25:40 | 2025-01-31 | 1899-12-30 12:25:40 |
| 5 | 2025-02-28 | 2025-02-28T16:25:40 | 2025-02-28 | 1899-12-30 13:25:40 |
| 6 | 2025-03-15 | 2025-03-15T16:25:40 | 2025-03-15 | 1899-12-30 14:25:40 |
| 7 | null | null | null | 1899-12-30 15:25:40 |
| 8 | 2024-02-29 | 2024-02-29T16:25:40 | 2024-02-29 | 1899-12-30 16:25:40 |
Same rows from the calculation and from the SQL in DuckDB.
Where a naive translation goes wrong
- Clock construction uses the 1899-12-30 date anchor.
Naive SQL
SELECT TIMESTAMP '1970-01-01 00:00:00'+hour*INTERVAL '1 hour'+minute*INTERVAL '1 minute'+second*INTERVAL '1 second' AS result FROM input ORDER BY shipment
shipment shipped received text result 1 2024-12-29 2024-12-29T16:25:40 2024-12-29 1970-01-01 09:25:40 2 2024-12-30 2024-12-30T16:25:40 2024-12-30 1970-01-01 10:25:40 3 2025-01-01 2025-01-01T16:25:40 2025-01-01 1970-01-01 11:25:40 4 2025-01-31 2025-01-31T16:25:40 2025-01-31 1970-01-01 12:25:40 5 2025-02-28 2025-02-28T16:25:40 2025-02-28 1970-01-01 13:25:40 6 2025-03-15 2025-03-15T16:25:40 2025-03-15 1970-01-01 14:25:40 7 null null null 1970-01-01 15:25:40 8 2024-02-29 2024-02-29T16:25:40 2024-02-29 1970-01-01 16:25:40 Matches the calculation
SELECT TIMESTAMP '1899-12-30 00:00:00'+hour*INTERVAL '1 hour'+minute*INTERVAL '1 minute'+second*INTERVAL '1 second' AS result FROM input ORDER BY shipment
shipment shipped received text result 1 2024-12-29 2024-12-29T16:25:40 2024-12-29 1899-12-30 09:25:40 2 2024-12-30 2024-12-30T16:25:40 2024-12-30 1899-12-30 10:25:40 3 2025-01-01 2025-01-01T16:25:40 2025-01-01 1899-12-30 11:25:40 4 2025-01-31 2025-01-31T16:25:40 2025-01-31 1899-12-30 12:25:40 5 2025-02-28 2025-02-28T16:25:40 2025-02-28 1899-12-30 13:25:40 6 2025-03-15 2025-03-15T16:25:40 2025-03-15 1899-12-30 14:25:40 7 null null null 1899-12-30 15:25:40 8 2024-02-29 2024-02-29T16:25:40 2024-02-29 1899-12-30 16:25:40
Signature
MAKETIME(hour, minute, second)