Skip to content

Roadmap

Ferro is pre-1.0 and under active development. The items below are known gaps we intend to close; priorities are driven by what users actually hit, so issues move things up this list.

Query Features

  • Aggregations beyond count()/exists() — sum, avg, min, max on the query builder. Today you either compute in Python after fetching or drop to raw SQL.
  • Partial selects — loading a subset of columns (User.select(User.id, User.username)-style) instead of full models, for wide tables and hot read paths.
  • Eager loading — prefetch_related/select_related-style relationship loading to eliminate N+1 query patterns. Today each awaited relationship attribute is its own query.
  • ilike() — case-insensitive pattern matching. Workaround: like() with normalized case.
  • not_in_() — NOT IN exclusion lists. Workaround: combine != comparisons with &.
  • Atomic update expressions — database-side expressions in batch updates, e.g. update(view_count=Post.view_count + 1), avoiding the read-modify-write race. Workaround today: load, mutate, save() (or raw SQL).

Connections

  • disconnect() — graceful pool shutdown for application shutdown hooks. Today cleanup happens at process exit.
  • Health checks — a check_connection()-style probe for readiness endpoints. Workaround: run a trivial query and catch the failure.
  • Richer pool configuration — PoolConfig covers max_connections/min_connections today; acquire timeouts, idle timeouts, and max connection lifetime are future work.

Influencing Priorities

None of this is on a promised schedule. If one of these gaps blocks you, say so on the issue tracker — a concrete use case is the strongest signal we get, and contributions are welcome.