TypeQL is the query language of TypeDB.
- Conceptual and intuitive. TypeQL is based directly on the conceptual data model of TypeDB. Its queries comprise sequences of statements that assemble into patterns. This mirrors natural language and makes it easy and intuitive to express even highly complex queries.
- Fully declarative and composable TypeQL is fully declarative, allowing us to define query patterns without considering execution strategy. The user only composes sets of requirements, and TypeDB finds all matching data to process.
- A fully variablizable language. Any concept in TypeQL has a type, and so any concept in TypeQL can be variablized in a query – even types! This enables TypeQL to express powerful parametric database operations.
- Built for consistency. TypeQL patterns are underpinned by a powerful type system that ensure safety and consistency of database applications.
For a quick overview of the range of statements that are available in TypeQL check out our TypeQL in 20 queries guide.
IMPORTANT NOTE: > > TypeDB & TypeQL are in the process of being rewritten in Rust. There will be significant refinement to the language, and minor breaks in backwards compatibility. Learn about the changes on our roadmap issue on GitHub. The biggest change to TypeDB 3.0 will be our storage data structure and architecture that significantly boosts performance. We’re aiming to release 3.0 in the summer this year, along with preliminary benchmarks of TypeDB.
TypeQL features the type system of the Polymorphic Entity-Relation-Attribute (PERA) model: entities are independent concepts, relations depend on role interfaces played by either entities or relations, and attributes are properties with a value that can interface with (namely, be owned by) entities or relations. Entities, relations, and attributes are all considered first-class citizens and can be subtyped, allowing for expressive modeling without the need for normalization or reification.
define
id sub attribute, value string;
email sub id;
path sub id;
name sub id;
user sub entity,
owns email @unique,
plays permission:subject,
plays request:requestee;
file sub entity,
owns path,
plays permission:object;
action sub entity,
owns name,
plays permission:action;
permission sub relation,
relates subject,
relates object,
relates action,
plays request:target;
request sub relation,
relates target,
relates requestee;Use subtyping to query a common supertype and automatically retrieve matching data. Variablize queries to return types, roles, and data. New types added to the schema are automatically included in the results of pre-existing queries against their supertype, so no refactoring is necessary.
match $user isa user,
has full-name $name,
has email $email;
# This returns all users of any type
match $user isa employee,
has full-name $name,
has email $email,
has employee-id $id;
# This returns only users who are employees
match $user-type sub user;
$user isa $user-type,
has full-name $name,
has email $email;
# This returns all users and their type
TypeQL's near-natural syntax and fully declarative properties make queries easily understandable, reducing the learning curve and easing maintenance. This allows you to define query patterns without considering execution strategy. TypeDB's query planner always optimizes queries, so you don't have to worry about the logical implementation.
match
$kevin isa user, has email "kevin@typedb.com";
insert
$chloe isa full-time-employee,
has full-name "Chloé Dupond",
has email "chloe@typedb.com",
has employee-id 185,
has weekly-hours 35;
$hire (employee: $chloe, ceo: $kevin) isa hiring,
has date 2023-09-27;TypeDB's TypeQL query language uses pattern matching to find data. Patterns in TypeQL are fully composable. Every complex pattern can be broken down into a conjunction of atomic constraints, which can be concatenated in any order. Any pattern composed of valid constraints is guaranteed to be valid itself, no matter how complex.
match
$user isa user;
match
$user isa user;
$user has email "john@typedb.com";
match
$user isa user;
$user has email "john@typedb.com";
(team: $team, member: $user) isa team-membership;
match
$user isa user;
$user has email "john@typedb.com";
(team: $team, member: $user) isa team-membership;
$team has name "Engineering";Note: All TypeDB Clients, as well as TypeDB Console, accept TypeQL syntax natively. If you are using TypeDB, you do not need additional libraries/tools to use TypeQL syntax natively. However, if you would like to construct TypeQL queries programmatically, you can do so with "Language Libraries" listed below.
- TypeQL Grammar
- TypeQL Language Library for Java
- TypeQL Language Library for Rust (under development)
- TypeQL Language Library for Python (under development)
- Documentation: https://typedb.com/docs
- Discussion Forum: https://forum.typedb.com/
- Discord Chat Server: https://typedb.com/discord
- Community Projects: https://github.com/typedb-osi
If you want to begin your journey with TypeDB, you can explore the following resources:
- More on TypeDB's features
- In-depth dive into TypeDB's philosophy
- Our TypeDB quickstart
TypeDB and TypeQL are built using various open-source frameworks and technologies throughout its evolution. Today TypeDB and TypeQL use Speedb, pest, SCIP, Bazel, gRPC, ZeroMQ, and Caffeine.
Thank you!
In the past, TypeDB was enabled by various open-source products and communities that we are hugely thankful to: RocksDB, ANTLR, Apache Cassandra, Apache Hadoop, Apache Spark, Apache TinkerPop, and JanusGraph.
Package repository hosting is graciously provided by Cloudsmith. Cloudsmith is the only fully hosted, cloud-native, universal package management solution, that enables your organization to create, store and share packages in any format, to any place, with total confidence.
TypeQL grammar and language libraries are provided under the Mozilla Public License 2.0 (MPL 2.0), and therefore freely usable without restriction when unmodified.
The full license can be founder at: LICENSE.