GraphEngine | Microsoft Graph Engine | Storage library

To my knowledge, there is no such standard way according to the documents, and the best practice also depends on our own requirements, e.g., performance or convenience. Here are my choices in different situations:

1. For a directed unlabeled graph which is a very common situation, I just use neighbors' cell ids (adjacency list) as a field. And I find it is very efficient for most graph operations;
2. For a directed graph with properties on the edges, there are two choices: use a list of values of self-defined struct, or set an individual cell for the edges and connecting the edges to the source/target node cells. The former one is practically faster than the latter one for most graph operations. But the cost is that it does not allow to access an edge without visiting the node cell, which is the benefit of the latter one;
3. For an undirected graph without properties on edges, for each edge (u, v), I place their cell ids in each other's adjacency lists;
4. For an undirected graph with properties on edges, a separate edge cell is set up for each edge, storing all the information on it including the associated nodes and properties;
5. For a hypergraph where an edge may connecting more than one nodes, my choice is the same as 4.

The introduced notion [GraphEdge] is used to recognize the edges by Language Integrated Knowledge Query (LIKQ), however, it will not affect our usages if our applications are not built on top of LIKQ.

@Andreas Hassmann, I had met a similar issue, so I guess your trouble may be caused by the ... in the foreach-loop.

I used an iterator like Global.LocalStorage.xxxCell_Accessor_Selector().Select(c => c.CellID.Value). In this case, the locks of the storage haven't been released which causes the deadlock when Global.LocalStorage.LoadCell() acquires the locks.

If your problem is exact the same as mine, the solution will be to apply .ToList() to the iterator.

Here are my codes to reproduce your problem.

The TSL:

Those attributes do not have an intrinsic meaning apart from the meaning you attach to them. "BaseType" does not make Apple derive from Fruit. You can just ask in your code for the value of the attribute "BaseType" on your cell.

It should be ReferencesIDs, not ReferenceIDs