TypeDB Studio

Select TypeDB edition below, and follow the instructions:

To select a database to work with, use the dropdown menu on the right of the database icon in the top toolbar. You can also create new databases here.

TypeDB Studio will automatically select a default database if there are no others present.

You can write TypeQL queries in the Query pane.

The Query pane contains a code editor that offers TypeQL highlighting and simple autocompletion.

When your query is ready to run, hit "Run query" in the Query pane.

Results are printed to the Run pane.

The Run pane offers three different views of results - you can choose between Log, Table and Raw.

The Log contains textual output, similar to TypeDB Console, as well as input log, and error messages.

Table view is well suited for visualising the answers of match and fetch queries in a tabular format, where each row represents an answer, and each column represents a variable.

Raw output allows you to see the raw HTTP response from TypeDB.

All queries and transaction operations are timestamped and logged to the History pane. Any errors that occur can be retrieved from this pane.

By default, transactions are fully managed by TypeDB Studio. A transaction opens when you start running a query, and commits when a schema/write query is done or closes when a read query is done.

For more fine-grained control, you can use the top bar to change the transaction mode from auto to manual. This allows you to open transactions, and perform multiple queries within a transaction before closing or committing.

Only one transaction can be open concurrently within a single instance of TypeDB Studio.

To connect, disconnect, or change connection settings, use the connection button in the top bar. While connected to TypeDB, the button changes its label to the server’s address or the custom name provided when setting up the connection.

Query-level errors are printed to Log Output. These are typically errors returned directly from TypeDB, and will contain detailed error codes and explanations of the problem (e.g: illegal TypeQL semantics)

Transaction-level errors will trigger an error popup notification.

Both types of errors can be viewed and copied to the clipboard by visiting the History pane on the Query page.