DuckDB 1.4.0 LTS

> Starting with this release, every other DuckDB version is going to be a Long Term Support (LTS) edition. For LTS DuckDB versions, community support will last a year after the release (for now). DuckDB Labs is also starting to offer support for older LTS versions after their community support has expired.

A fixed date is great - but it's difficult to see a single year as "long term" support.

Will be interesting to what commercial support options will emerge.

▲

ZeroCool2u 2 hours ago | parent | prev | next [-]

The Fill function for interpolation is really nice, but there's so many different ways to perform interpolation I'd like a lot more detail on what methods are available and which is used by default.

	▲	tanelpoder 5 minutes ago \| parent [-]
		Indeed. Previously, when computing latency histograms from sampled events, I've abused DuckDB SQL cross join/cartesian products to generate zero values for "empty buckets" within a single SQL statement [1]. But makes the SQL unnecessarily complex & slower too, so I quickly moved that empty bucket rendering functionality to the frontend... [1]: Example DuckDB SQL with generated bucket lists and cross join + outer join: https://github.com/tanelpoder/0xtools/blob/master/tools/sql/...

▲

datadrivenangel an hour ago | parent | prev [-]

LTS is a move in the right direction. One year is somewhat short, but with no backwards breaking changes that's fine.