Skip to content

chore: release hotdata-materialized v0.1.0 #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
eddietejeda merged 1 commit into from
Jul 22, 2026
Merged

chore: release hotdata-materialized v0.1.0 #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

## [0.1.0] - 2026-07-22

- `@materialize` decorator and `MaterializedFrame`: write-behind caching of
expensive Django query results into Hotdata; hits return Arrow-backed
frames (`.arrow()/.df()/.to_pylist()`), `.sql()` runs server-side against
Expand All @@ -18,3 +20,4 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Remote registry (no migrations or local state in the host app) and
one-managed-database-per-entry storage with TTL expiry backstop
- TPC-H demo project benchmarking direct Postgres vs the cache

Loading