James Whiteside
James Whiteside
## Problem to Solve Some simple queries are difficult to express in TypeQL, and present a significant barrier to the early user journey. This issue will serve as a place...
## Description When inserting two ownerships of the same unique or key attribute by the same owner, TypeDB throws an error. This should not be the case as attribute idempotency...
## Problem to Solve Currently, these is no way to output the results of a query into TypeQL, for instance: ``` match $p isa person, has $a; ``` ``` $p_1...
## Description If I run a match-insert query against a database and the match fails, the server gives a normal response, even if the insert pattern is not valid. Example...
## Description When executing a query with a large number (75,264) of answers, the client takes over a minute to receive the results, but when counting the results server-side, the...
## Description The following query throws a null pointer exception: ``` match $x type entity; $g isa gene, has official-gene-symbol $s; not { $x type relation; $t isa tissue, has...
## Description Non-inferred concepts are incorrectly marked as explainable by `conceptMap.explainables()`. Attempting to explain those concepts with `transaction.query().explain()` returns an empty result. This is easily worked around, but can cause...
## Problem to Solve When determining why a conclusion came about based on a complex set of rules, it is currently difficult to retrieve the base facts that caused the...
## Description Some transactions lead the server to hang. This behaviour is inconsistent, with the same query sometimes completing or sometimes hanging. In Studio, the concept graph is sometimes returned...
## Problem to Solve Currently, parsing of a string containing multiple concatenated queries (as in TypeDB Studio) has the possibility to generate ambiguous results. Specifically: (`match`, `insert`) cannot be distinguished...