James Whiteside

@flyingsilverfin With the following schema: ``` define person sub entity; membership sub relation; membership relates member; club-membership sub membership; person plays club-membership:member; ``` `person` instances can play the `member` role...

I wonder if we should implement `@card(1)` as default for all edge-defining keywords, not just `relates`. I've tried a small example and found I had to stick in on nearly...

Yeah I was just opening the discussion. The fact you've come back with a counter-example that quickly is probably a good sign that `@card(1)` default is a bad idea.

This was implemented in Workbase (a long time ago).

Reproduced with the following steps: 1. Used [https://github.com/james-whiteside/typedb_iam](https://github.com/james-whiteside/typedb_iam) 2. Ran a query in Studio involving rule-inference that created a high number of inferred things: ``` match $p isa person, has...

**Update with TypeDB Cloud 2.24.17 and Studio / Python 2.24.15** - `SRV27` is no longer thrown by either Studio or Python API. - No errors are thrown with Python API....

This is very much not the case. The two have completely different applications and I wouldn't have opened this issue if I thought this would be addressed by fetch. The...

Having looked into this further, it is actually impossible to generate TypeQL responses on the client side in the general case, even with the context of both the query and...

The missing info is because of inference of roles. The concept map does not contain edge information. While `owns` edges can be reconstructed from the query pattern, because the type...

Exactly what I'm trying to do, and yes this contains all the info necessary to build a graph with no further calls. They look identical because a graph is just...