Understanding behavior of recursive functions
I am trying to see if I can get a better understanding of this example
```
fun transitive_places($place: place) -> { place }:
match
{...
Destructuring relation types in match statements.
Is there any semantic difference between the following two queries?
```
match
$user isa user, has id "u0003";
(located: $user, location: $place) isa locating;...
Modeling layered and meta graphs
Sorry to get cut off @vpavlyshyn !!
Here's a little schema that could be used:
```
define...
Interface and inheritance types
@vpavlyshyn Here are some resources to explain inheritance types: https://typedb.com/docs/core-concepts/typeql/entities-relations-attributes#_inheritance
Polymorphism:
https://typedb.com/docs/core-concepts/typeql/entities-relations-attributes#_polymorphism...
Reducing with 0 when value is not there
question for the non-existent values:
when we sum over an attribute, say payment and for some records that this value is non-existent (which i believe typedb doesn't create any instance of that attribute for that particular entity?), how can i set 0 for those cases in my sum? I don't care about my entity just in my sum i want to replace n/e with 0.
here is a query, where $pa could be non-existent for some records:
```
match...
How to use `analyze()`?
In the documentation link here there is a mention of
analyze() function.
Suppose I have the following query.
```...How production-ready is TypeDB?
I plan to migrate most of my businesses databases from Postgres to TypeDB, since its model is so much better for everything I do. I need to store and query a lot of data, and there are lots of proven solutions for doing these things fast in SQL. How are the benchmarks of TypeDB compared to some SQL solutions?
Another thing that I didn't see a lot of, is migrations. I expect to be changing the ontologies of my database over time, and its not so clear to me what happens if I change the types of my data that already exists....
Encompassing RDF/OWL
We aim to build a layered stack of TypeDB databases for different cybersecurity protocols, like a pancake stack, each layer with a specific protocol for representing a particular aspect of the whole. Unified, they enable you to capture data and reason over the many aspects of the causal picture behind a successful threat.
Two of the standards we wish to embody in TypeQL, SPYDERISK and Mitre D3FEND are published as rdf/owl standards in turtle files, Our basic plan was to manually re-implement and improve on SPYDERISK in TypeQL, and to separately build a transpiler to dynamically convert the Mitre D3FEND rdf/owl into TypeQL, including converting the DL to functions.
Ideally, this transpiler could include some sort of test harness that could test the results of queries/reasoning to test they were identical. This is a long-term aim, because during the Grakn Warrior days, we had investigated deeply the porting of the Semantic Arts gists over, in a provable way....

Storing and retrieving lists of entities
Moving from: https://discord.com/channels/665254494820368395/699946888572567611/1413211154020565002
From @nphair @kevinsullivan
Hi all, is there a general strategy you recommend for converting from inductive data types to typedb's ER model?
...