orbital vs TimescaleDB

orbital converts a fitted tidymodels workflow into a database expression so prediction runs where the data lives, no R session in the loop. Its value is entirely a function of coverage, and 0.5.0 was the largest coverage release yet: catboost and lightgbm boosted trees, rpart decision trees, earth-backed MARS, glmnet multinomial regression, and both randomForest and ranger random forests, all for numeric, class, and probability predictions. The 0.5.1 follow-up is corrective, fixing SQL that Snowflake and other engines rejected because it cast booleans directly to numeric.

The package has been working outward in rings: recipe preprocessing steps first, then model types, then post-processing via the tailor package in 0.4.0, with show_query() added so users can inspect what actually gets sent. Recent releases show the constraint shifting from R-side translation to SQL dialect compatibility — the bugs now are about what a specific database will accept, not whether a model can be expressed. estimate_orbital_size() in 0.5.1 acknowledges the other practical limit, since generated expressions can grow large enough to matter before you generate them.

With the major boosting and ensemble engines covered, expect the next releases to keep chasing dialect-specific SQL correctness across warehouses rather than adding model families.