Christoph Dorn
Christoph Dorn
## Problem to Solve TypeQL is missing a `union` keyword. This is a basic feature of, e.g., SQL, Cypher, and other query languages. From a practical perspective, the `union` keyword...
## Problem to Solve TypeQL is missing a satisfiability check which verifies whether a pattern can be satisfied, or equivalently, a double negation statement `not { not {...} }`. Both...
## Problem to Solve TypeQL is missing user-defined data integrity constraints. Such constraints mirror complex dependencies between data. Well-studied dependencies, e.g., include the following (some of these may be addressed...
## Problem to Solve We want to address several shortcomings in TypeQB at the same time: * *Nesting of queries*: call queries from other queries. * *Using aggregates in queries*:...
## Changes Added specification of the TypeDB 3.0 database system behaviour. ## Implementation See file `spec.md`.
# Collection of proposed syntactic sugar TypeQL is often verbose. This issue collects various useful abbreviations. Syntax is based on the current TypeDB 3.x `spec.md` ## Inline attributes: **Goal**: simplify...
## Problem to Solve > ***Grouped aggregations are a core data analysis command*** In its current specification, TypeDB "almost" supports this features, but it could be made much more convenient....
## Trait types **Goal**: Allow users to refer to traits (interface types) in function signatures. **Analogy**: `dyn Trait` in Rust. **Suggestion**: ``` define fun my_fun($x : owns name) -> long:...