typedb
typedb copied to clipboard
vaticle
TypeDB: the polymorphic database powered by types
## Problem to Solve ( A slightly different version of #6792 ) Often, the way users write rules leads to the reasoner proving more facts than required. The classic example...
## 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...
## Description When we delete or change a `Rule` using `delete()` or `setLabel()` method and then use `LogicManager::getRule()`, it returns the unchanged rule from the `LogicCache`. Cache is reindexed only...
## Description In a schema ``` define ownership sub relation, relates owned, relates owner; group-ownership sub ownership, relates group as owned, owns ownership-type; object-ownership sub ownership, relates object as owned,...
## Problem to Solve With active development of a database schema, it can be hard to track all the versions of a schema. While for files it's not a problem...
## Problem to Solve Currently, concludables which share a variable are combined into a single retrievable before the reasoner-planner is invoked. This means the planner can must plan the whole...
## Problem to Solve As of https://github.com/vaticle/typedb-behaviour/pull/239 and follow up tweaks, we have several definitions that look something like this: ``` @Then("{root_label}\\( ?{type_label} ?) get owns attribute types with annotations:...
## 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...