We have upgraded to TerminusDB 11 – This is a very big release, and you should pay careful attention to upgrade information as the storage back-end has changed and requires an upgrade.
After installing this version, you will also need to upgrade your storage directory, or the server will not start. A conversion tool is provided at https://github.com/terminusdb/terminusdb-10-to-11. This is also bundled with terminusdb-bootstrap so you can pull the latest bootstrap to upgrade.
TerminusDB 11 now responds to `xsd:integer`, `xsd:decimal`, and all of the unbounded sub-types of these two objects in the document interface with strings. This is because many (even most) JSON libraries can not handle arbitrary precision integers, and few (if any) can handle arbitrary precision floats. It should still be possible to submit documents using integers or floats, but when returned they will be strings.
See what’s changed in the TerminusDB 11 release notes.
- New Storage backend
- Added typed storage for a wide variety of XSD types, reducing storage overhead and improving search performance
- Introduce a layer archive format reducing storage use and latency and simplifying interchange.
- GraphQL `_type` added to objects to return the exact rather than subsumed type
- Added `@unfoldable` document flag to frames
- Add `@metadata` to frames
- Fixed a bug in inverse fields in GraphQL
- Removed extraneous system objects from GraphQL schema
- Improved completeness of GraphQL schema handling
- Added x-method-override header to CORS
- Fixed GraphQL naming bug leading to GraphQL schema crashes