-
## Problem to Solve
There are two problems to solve with this issue:
1. Marketing - When coming to sell a TypeDB solution I see I face two questions. The first is why graph data and then why Typ…
-
## 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 to collate them.
## Exam…
-
## Problem to Solve
We collect the agreed list of changes and requirements that will be in the first version of TypeDB 3.0.
## Changes
### API
- https://github.com/vaticle/typedb/issues/…
-
## Problem to Solve
Implement TypeQL parsing in languages other than Java. This would for instance allow reading entire files of queries into the python or node client without having to hack some cus…
-
## Problem to Solve
There used to be a Graql cheat sheet to look at many aspects of the Graql syntax at once. The following link doesn't work: http://grakn.ai/graql/graql_cheatsheet
## Current …
-
See test in test_refactor
```
def test_translation_campaign(self, setup_teardown, generate_connection):
typedb_sink = TypeDBSink(connection=generate_connection,
…
-
## Description
Strings are not escaped when converting Java TypeQL to a query string, despite requiring escape characters in order for the query string to be valid.
It also appears that the requ…
-
## Description
Calling `match` and `delete` with one variable, and `insert` with another, results in a TypeQL Error. The `insert` should be independent of the `match` and `delete`.
## Environmen…
-
## 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 for most use…
-
Has the GRAKN team ever thought to implement natural language to graql via machine learning models and datasets similar to https://github.com/salesforce/WikiSQL and other efforts using [SQL ](https://…