-
_This issue was originally posted by @haikalpribadi on 2018-04-05 14:23_.
-
## Description
In the rule-validation logic, we have assertions which would fail in the presence of nested negations in rules. These would fail during testing but would not in prod - potentially allo…
-
## Problem to Solve
Exceptions need more granular types.
E.g. I run the query `match $t sub {my_type};` with a user-defined string `my_type`. If I get `TypeDBClientException`, is it because the …
-
_This issue was originally posted by @tomassabat on 2018-08-19 17:30_.
Load dataset called "grakn-dist-1.3.0 [Tomas Biomed v2]" (keyspace "disease_james") in folder Datasets in Dropbox and run the…
-
Please replace every line in curly brackets ( { like this } ) with appropriate answers, and remove this line.
## Description
While using TypeDB Studio creates xxx.tql file and inputs some Chines…
-
## Description
Running a query produces an unhandled exception. The notable feature here is that there is a role-player inside rule conclusions that is left un-declared, to be inferred by type infe…
-
This would be a way to solve lots of non workaroundable issues and performance drops, both in queries and mutations.
# The problem
## Queries
- When querying multiple entities, we are forced to …
-
## Problem to Solve
The grammar allows `match ... ; sort $x, $y, $z asc/desc;`. However, we should allowing each sort variable to have its own direction: `sort $x asc, $y desc, $z asc;` for example…
-
We should have a relationship in TypeDB/TypeQL that represents all descendants of a BPMN/XML tag, so that we can query all BPMN/XML tags associated to a Mission (conceptual model) or BPMN definition.
-
Current version of the [concept model TypeQL](https://github.com/cardialfly/DALNIM/blob/main/concept_model.tql) declares
`PrecedenceTask sub entity;`
This does not seem to match with the [conce…