Joshua Send
Joshua Send
## Problem to Solve TypeDB's connection model introduces needless complexity, as well as some states of questionable use (such as a `schema` session + `read` transaction). ## Proposed Solution We...
## Problem to Solve TypeDB currently does not support a very expressive set of value types for attributes, which makes defining complex values (such as 'coordinate's) difficult. ## Current Workaround...
## Problem to Solve Currently there is no way to operate over ordered collections in TypeDB. We address one aspect of this, which is ordering role players within relations. ##...
## Problem to Solve We aim to make our TypeQL queries more consistent and expressive, reformulating them in terms of streams/iterators commonly known from programming languages, also allowing them to...
## Problem to Solve The maintanance and extension surface area of drivers' Concept API is extremely high while the its usage is extremely low, now that TypeQL fetch handles optionality...
## Problem to Solve TypeQL doesn't have a way to represent enums, or even values restricted to a set of values for an attribute, a very common use case (example:...
## Problem to Solve Currently there is no way to operate over ordered collections in TypeDB. We address one aspect of this, which is ordering attribute ownerships. ## Current Workaround...
## Problem to Solve TypeDB currently does not have a way to automatically enforce compound keys, nor does it have a way of enforcing uniqueness of relations. ## Current Workaround...
## Problem to Solve Currently, users have to manage deletion of dependent/connected relations manually when deleting entities or relations. ## Current Workaround Users have to manually query for connected desired...
## Problem to Solve This issue is replacing https://github.com/vaticle/typedb/issues/6766 after further discussion and refinement. We, and our users, often face the issue of having to manually clean up attributes if...