TerminusDB 11.0.6 turns schema changes into automatic data migrations: update a class and TerminusDB infers the migration for existing documents. It was released on 3 May 2023.
- Inferred migrations — schema changes carry their data transformation with them.
- Migration options —
allow_destructive_migrationandrequire_migration. - Paged diffs —
startandcounton the diff endpoint.
Inferred migrations
What it does
When you modify classes through the document interface, TerminusDB now infers a migration where possible — renames, retypes, weakening constraints — and applies it to the instance data already in the database. No separate migration script.
Why it matters
Migrations make schema change a lot easier and more reliable, as they automatically transform existing data to match the new schema and the same can be applied when moving data between branches or databases.
Read more: Schema migration reference
Migration options
Two new options on the document interface:
allow_destructive_migration— permits migrations that modify existing instance data; the schema change transforms objects already stored.require_migration— fails the request when no migration can be inferred, instead of silently accepting a schema change that leaves data behind.
Paged diffs
The diff endpoint gains start and count options for paged results — handy for large diffs between distant commits.
Read more: JSON diff and patch
Fixes
- GraphQL: unused optional properties, enums in collections, and
@oneOfproperties now work; stale@oneOfobjects are cleaned from the schema graph - Diffing
Setvalues now works - Memory leak fixed in the document API; crash on several compressed requests in one session
- Better error when pushing to a nonexistent remote
Upgrade
docker pull terminusdb/terminusdb-server:v11.0.6No data migration is needed. Docker install guide · Full changelog on GitHub
Previous: TerminusDB 11.0.4: The Document History API · Next: TerminusDB 11.1.0: Semantic Indexer and Layer Concat · TerminusDB 11.0 changelog · Release index