Joshua Send

**DO NOT MERGE** We have decided to park this change since it practically breaks backward compatibility of TypeDB: user's that did string escape previously have databases containing `quoted \" value...

We have further considerations for when this issue comes back: #239 fixed this for now, but have to settle on a behaviour of how to actually insert a newline character...

Hi there - this issue is not clear: do you want to make all relations transitive by default? You can do that with ``` when { ($role-1: $a, $role-2: $b)...

The main concern right now is that we aren't actually able to store a string containing " AND ' within a Graql string without a backslach being stored in Grakn...

Just came across this! I wanted to put out that we've independently come up with a solution to the problem of Bazel/Crate deployment interopability. Granted, it works for a specific...

TypeDB 3.0 ## Problem to solve TypeDB should offer a sort of auto-generated attribute value, such as auto-increment. This should be defined at the `owns` level, rather than the attribute...

Note: `auto-increment`/`serial` falls under the domain of defaulting values in most databases

I agree that `onWrite` rules are something we've been percolating for a while ;)

Heads up: sorting on non-string values (and also not using reasoner) is now optimised natively in TypeDB :)

yeah anything to do with ordering will be best optimised with sorted numbers