Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
Comparison · Analytics
labelled vs TimescaleDB
A side-by-side editorial comparison of labelled and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
labelled vs TimescaleDB: at a glance
What is labelled?
The bridge between Stata/SPSS labelled data and tidy R keeps widening, one integration at a time.
labelled manages variable labels, value labels and user-defined missing values on data imported from Stata, SPSS and SAS, filling the gap between those formats' metadata and R's native types. Recent releases have pushed outward from the core label accessors: survey design objects from the survey package are now supported throughout, look_for() results can be rendered as formatted gt tables, and dictionary data frames convert in both directions. Error messaging moved wholesale to cli in 2.14.0.
What is TimescaleDB?
TimescaleDB is paying down correctness debt in its columnstore query paths.
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
labelled vs TimescaleDB: editorial side-by-side
labelled
0.0ANALYTICS
The bridge between Stata/SPSS labelled data and tidy R keeps widening, one integration at a time.
◆ Current state
labelled manages variable labels, value labels and user-defined missing values on data imported from Stata, SPSS and SAS, filling the gap between those formats' metadata and R's native types. Recent releases have pushed outward from the core label accessors: survey design objects from the survey package are now supported throughout, look_for() results can be rendered as formatted gt tables, and dictionary data frames convert in both directions. Error messaging moved wholesale to cli in 2.14.0.
◆ Where it's heading
The arc is toward being usable wherever labelled data ends up, not just where it is loaded. Each recent release either extends support to another object type — survey designs, packed columns, plain vectors, tibbles with list columns — or adds a conversion path between labels and some other representation. The look_for() search function has become a second centre of gravity alongside the label accessors, accumulating its own output formats and long-format conversions.
◆ Prediction
The pattern of adding compatibility with one more object type or output format per release is stable and likely continues. Nothing in these entries indicates a change to the underlying haven_labelled representation the package is built on.
TimescaleDB
5.0ANALYTICS
TimescaleDB is paying down correctness debt in its columnstore query paths.
◆ Current state
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
◆ Where it's heading
The feature work of 2.27 and 2.28 - vectorized filter evaluation, first/last derived straight from columnstore batch metadata, sparse indexes, SkipScan on compressed data - has been followed by a steady stream of fixes to those same code paths. 2.29.2 alone repairs SkipScan dropping uncompressed rows, sparse-index pushdown returning wrong results for IS NULL, and gapfill over window aggregates. That is the normal cost of pushing query optimizations into a compressed columnar store, and the project is working through it release by release rather than pausing.
◆ Prediction
With three consecutive patch releases on the 2.29 line and no new highlighted features since 2.29.0, the next minor is likely to resume the columnstore performance work - though the density of wrong-results fixes suggests more patches first.
Alternatives to labelled and TimescaleDB
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either labelled or TimescaleDB.
silx
silx settles into maintenance a release after its PySide6 migration
Plotly
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread
aniread stops asking you to know which tracker wrote the file
Rho
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
See all labelled alternatives → · See all TimescaleDB alternatives →
Recent activity from labelled and TimescaleDB
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoTimescaleDB2.29.2: SkipScan and sparse-index correctness fixes
- 15d agoTimescaleDB2.29.1: security fixes plus compression bugfixes
- 19d agoTimescaleDB2.29.0: chunk exclusion speeds up UPDATE and DELETE
- 1mo agoTimescaleDB2.28.3: columnar pipeline correctness fixes
- 1mo agoTimescaleDB2.28.2: upgrade-path fixes for 2.28.1
- 1mo agoTimescaleDB2.28.1: compressed-table crash and constraint fixes
- 10mo agolabelledFormatted look_for() tables and two-way dictionary conversion
- 11mo agolabelledSurvey design objects supported across the package
- 1y agolabelledRegression in set_variable_labels() corrected
- 1y agolabelledcli adopted for all messaging; null_action gains options
- 2y agolabelledCustom functions can rewrite variable and value labels in bulk
- 3y agolabelledPacked columns supported and label attributes exposed directly
Frequently asked questions
What is the difference between labelled and TimescaleDB?
They serve adjacent needs but don't currently overlap on shipped themes. TimescaleDB is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is labelled better than TimescaleDB?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. TimescaleDB is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to labelled?
Top labelled alternatives in Analytics are ranked by recent ship velocity. Browse the "labelled alternatives" section above for the current picks, or visit /alternatives/labelled for the full list with editorial commentary on each.
What are the best alternatives to TimescaleDB?
Top TimescaleDB alternatives in Analytics are ranked by recent ship velocity. Browse the "TimescaleDB alternatives" section above for the current picks, or visit /alternatives/timescaledb for the full list with editorial commentary on each.