Krishnan Govindraj

This is likely due to the way the traversal engine handles negations - it finds all answers to the unnegated section (in this case `$p isa person;` and then executes...

At the current state of the reasoner (2.14.3), I believe we are as efficient as can be. Consider the case of undirected transitivity (as mentioned) to create co-dependent cycles ```...

My previous comment likely misunderstands it. Specifically: "I believe all of these are required to be evaluated for correctness" What the issue suggests is to detect when all orders are...

This is still valid, and a different issue to that fixed by #6790

Point 5 is a duplicate of https://github.com/vaticle/typedb/issues/3257 Schema level constants / types having attributes sounds like a valid feature request. Hence keeping this issue.

The broken symmetry asks the question: Is there not a case to restrict the number of owners (of a given type) for a given attribute? [`@unique`](https://github.com/vaticle/typedb/issues/6658#issuecomment-1473903616) is a case where...

> I wonder if we should implement @card(1) as default for all edge-defining keywords ^ I would say this makes sense for attribute ownership, but not for plays as that...

I know the comment is 2 years old, but I had a different understanding. Bob and Alice only exchange public keys with each other. The private keys remain secret. If...

The exception here says nothing about the syntax expected. Could you re-run it with the `transaction.logic` -> `transaction.native_object` rename and post the syntax error (if it happens).