Multiple DATE_PART extraction #2779
Comments
hawkfish
pushed a commit
to hawkfish/duckdb
that referenced
this issue
Dec 20, 2021
Implement for TIMESTAMP, DATE, TIME and INTERVAL. Tweak promotion weights to prefer VARCHAR to LIST.
hawkfish
pushed a commit
to hawkfish/duckdb
that referenced
this issue
Dec 20, 2021
Implement for TIMESTAMPTZ. Some minor code cleanup and templatisation. Expand test data.
hawkfish
pushed a commit
to hawkfish/duckdb
that referenced
this issue
Dec 21, 2021
Handle hostile date part LISTs.
hawkfish
pushed a commit
to hawkfish/duckdb
that referenced
this issue
Dec 22, 2021
Filter out unneeded expensive date calls.
hawkfish
pushed a commit
to hawkfish/duckdb
that referenced
this issue
Dec 23, 2021
Benchmark ICU structs.
hawkfish
pushed a commit
to hawkfish/duckdb
that referenced
this issue
Dec 23, 2021
Reduce writes to improve performance.
hawkfish
pushed a commit
to hawkfish/duckdb
that referenced
this issue
Dec 25, 2021
Check for illegal parts and return 0 for time zone offsets.
hawkfish
pushed a commit
to hawkfish/duckdb
that referenced
this issue
Dec 28, 2021
Improve coverage and fix a few small bugs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Date part computations are slow and often have to compute multiple parts, so it would be nice to have another implementation of
DATE_PARTthat takes a (constant)LIST<VARCHAR>of part names as the first argument and returns aSTRUCT<part:BIGINT,...>containing all the named parts in the order given.The text was updated successfully, but these errors were encountered: