Joshua Send
Joshua Send
## Problem to Solve We should disallow disconnected match queries, since these are usually user errors. In particular, when combined with data writes such as deletes, a 'match' query generating...
## 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 In some data models, attributes are indendent domains that can be made to exist without any connections or ownerships - eg. inserting all valid names in...
## Problem to Solve The terms 'thing' and 'type' can be removed from the public interface of TypeDB and TypeQL. ## Proposed Solution The public APIs of TypeQL and TypeDB...
## Problem to Solve To complete TypeDB's internal data model, which includes RoleType as a type that has instances, TypeDB 2.x includes actual role _instances_, which are represented as vertices...
## Problem to Solve One major performance bottleneck of TypeDB is the structure of relations: to traverse through relation, we always have to go from a player, to the role...
## Problem to Solve There is an inconsistency in the attribute type definition: we allow the root `Attribute` type to be valuetype-less, and abstract. All user attribute types derive from...
## Problem to Solve GraphQL is a standard for querying and returning graph-structured answers to the caller. TypeDB and TypeQL are currently far removed from being able to query and...
## Problem to Solve Currently, we use `GraknException`, which is a `RuntimeException`, and catch it in the `QueryManager`, which is a strange behaviour. We should only be catching `CheckedException`s. This...
Because of the changes noted in https://github.com/vaticle/bazel-distribution/pull/372, we no longer have a consistent behaviour: NPM deployment works either with username/password OR tokens depending on the environment variables provided. To attempt...