TerminusDB 11.0.4 adds a history API that tells you when a document changed, and an experimental schema migration endpoint. It was released on 12 April 2023.
- History API — find out when an object changed.
- Experimental schema migrations — transform existing data when the schema evolves.
History API
What it does
GET /api/history/<path> answers "when did this document change?" by listing the commits that touched a given document. It is the per-record view of the commit log — the basis for audit trails and time-travel queries. Later releases extended it with diff output and streaming.
Why it matters
Understanding specifically when a particular document changed and how it changed is important for audit trails and compliance, and for safe experimentation, always making it easy to get back to a known good version, thanks to the change message, and to branch out to create new versions of the data.
Read more: Audit a database's history · Versioned search history
Experimental schema migrations
A new endpoint migrates a schema and transforms existing instance data to match — not only validates it. Schemas can also be updated from a target branch as long as a migration exists. This experiment grew into the automatic migration inference of 11.0.6.
Read more: Schema migration reference
Enhancements
- Loaded layers are kept in an LRU cache for faster repeated queries
- Optimize now also optimizes schema layers; better memory use during commits and squashes
Upgrade
docker pull terminusdb/terminusdb-server:v11.0.4No data migration is needed. Docker install guide · Full changelog on GitHub
Previous: TerminusDB 11.0.3: The Patch Endpoint · Next: TerminusDB 11.0.6: Automatic Schema Migrations · TerminusDB 11.0 changelog · Release index