TypeDB 3.0 is live! Get started for free.

TypeDB 2.x to 3.0

TypeDB 3.0 is a major leap forward, offering significantly improved performance and introducing a wide range of changes across almost every aspect of the database. This page outlines the key updates you should know, alongside recommendations for server and driver upgrades.

Migration process

  1. Review the missing features list before starting your migration. Some features might not yet be available in 3.0, and you may need to wait for a newer version to proceed.

  2. Understand the scope of changes by referring to the major changes section.

  3. Export your schema and data from TypeDB 2.x using the export manual.

  4. Data migration guide and tools are in progress. Full migration of a production database is currently unsupported. Stay tuned for updates!

  5. (Optional) Refresh your knowledge of TypeDB and TypeQL by following the updated Quickstart Guide.

  6. Set up TypeDB 3.0 by following the Configuration Manual. The setup process remains largely unchanged from 2.x.

  7. Manually update your schema definition file. Use error messages during application to guide adjustments. The major changes section highlights the most common updates needed.

  8. (Optional) Update your supporting queries using the Schema and CRUD manuals.

  9. (Optional) Update your drivers. Consult the Drivers Manual and the major driver changes list for details.

Major changes

This section highlights changes from TypeDB 2.x, not all new features in 3.0. Explore the Manual, TypeQL Documentation, and release notes for the full picture. Stay tuned for upcoming blogs showcasing new features!

Click on a feature below for detailed documentation and examples.

TypeDB and TypeQL

  • Sessions Removed: Connections to TypeDB now only require opening a schema, write, or read transaction.

  • Integer Value Type Renamed: long is now integer.

  • Kinds Introduced: no more predefined root types and their subtyping through person sub entity, friendship sub relation, or name sub attribute. Each new type should be declared with an explicit kind: entity person, relation friendship, and attribute name. Check out Schema modeling for more.

  • Expanded User Management: Authorization and user management are now included in all TypeDB editions. Default credentials, if applicable, can be found in the Connection Manual.

  • Updated Query Syntax:

    • undefine and delete now explicitly "point" to their removed targets, reducing ambiguity.

    • fetch syntax aligns with JSON output formatting.

    • match produces visible row-like results itself (similarly to insert, etc): no more get s!

    • All $vars start with $: no more ? for value variables! However, it is still easy to differentiate their declaration with the new let keyword. Check out some read queries examples here.

  • Annotations and Statements Consolidated: abstract and regex are now grouped under @annotations.

  • Smoother trait specialization:

    • It is possible to redefine already inherited owns and plays on subtypes, adding more annotations to them.

    • As before, use the as keyword to specialize a relates.

  • Default Cardinalities:

    • Default cardinalities are applied to owns, relates, and plays if not explicitly defined.

    • Default plays cardinality: @card(0..) (unlimited).

    • Default owns and relates cardinality: @card(0..1) (up to one instance). Explicitly define cardinalities for traits expecting multiple instances to avoid data corruption and optimize database performance.

  • Rules and Inference Replaced: Rules are now replaced by functions, requiring explicit functions execution instead of inference, but offering more abstraction and flexibility.

TypeDB Drivers

API Simplification for smoother UX and better maintenance.

  • Now, all schema and data fetching and modifications are performed through a single transaction.query("your query") interface.

  • No more query().insert() and query().define().

  • No more concept.delete() or concept.getHas().

  • Concept structure is preserved (the only difference: Thing is renamed to Instance), casts are available, and it is possible to retrieve something simple as a type’s label or an attribute’s value, that are sent with the type itself.

  • In OOP languages (like Java and Python), concepts have try versions of their methods, available for any concept and returning optional results. Using casting, the concrete methods returning results directly become available, as in 2.x.

Temporarily missing features

This section contains the list of features that were introduced in 2.x, but are still under development in 3.x. Coming soon! Take into account that some of your processes can be blocked if you previously relied on these features.

TypeDB and TypeQL

  • Database import and export tools.

  • Configuration files (use CLI as a temporary solution).

  • Transaction options.

  • update queries (use delete + insert as a workaround).

  • contains and like operators for string s.

  • Instantiation restriction for inherited owns and plays (used to as). A better way is planned to be released in the future (NOTE: you don’t need the as keyword to specialize an ownership of an inherited super attribute type with an ownership of its subtype).

  • Scaling support for Cloud and Enterprise editions.

TypeDB Drivers

  • Node.js, C, C++, and C# drivers are not yet available.

TypeDB Studio

  • Graph visualizer has been disabled due to incoming migration to an IDE plugin. Please consider using side tools for graph visualization if required.

  • Type browser is temporarily unavailable and planned to be reimplemented in the IDE plugin.

Having troubles?

For troubleshooting tips and guidance, refer to the Troubleshooting Manual.