DuckDB 1.5.0
duckdb.org
DuckDB 1.5.0
1–6 of 6 posts
Re: DuckDB 1.5.0
#2Still no support for range types though, which is a pity as that continues to block me from porting most of my Postgres workloads.
date_ranges are so great, you'll wonder how you ever did without them.
Re: DuckDB 1.5.0
#3Still no support for range types though, which is a pity as that continues to block me from porting most of my Postgres workloads. date_ranges are so great, you'll wonder how you ever did without them. 1: https://www.postgresql.org/docs/current/rangetypes.html 2: https://github.com/duckdb/duckdb/discussions/6077
I forgot no say that I really hope they make it into the 2.0 release later in the year.
Re: DuckDB 1.5.0
#4Congrats! It's so underestimated engine.
Re: DuckDB 1.5.0
#5Still no support for range types though, which is a pity as that continues to block me from porting most of my Postgres workloads. date_ranges are so great, you'll wonder how you ever did without them. 1: https://www.postgresql.org/docs/current/rangetypes.html 2: https://github.com/duckdb/duckdb/discussions/6077
Once again, I cry for what I don't have in SQL Server. Range types look cool!
Re: DuckDB 1.5.0
#6Still no support for range types though, which is a pity as that continues to block me from porting most of my Postgres workloads. date_ranges are so great, you'll wonder how you ever did without them. 1: https://www.postgresql.org/docs/current/rangetypes.html 2: https://github.com/duckdb/duckdb/discussions/6077
Once again, I cry for what I don't have in SQL Server. Range types look cool!
Another thing you are apparently missing is deterministic ordering for tied elements:
https://modern-sql.com/blog/2026-03/order-equivalence-over-c...