This issue should hopefully be resolved in the next patch of TypeDB!
1 Like
Officially out now: The TypeDB 3.0 Roadmap >>
This issue should hopefully be resolved in the next patch of TypeDB!