A subgraph in the database is basically a forward cached instance of
selected nodes and edges in an in-memory graph
(visgraph.graphcore.Graph). This object may then be used for traditional
path tracing without going back to the database.
Any modifications to graph element properties *will* be synchronized
back to the database backing the given subgraph.
|
|
|
|
|
addNode(self,
nodeid=None,
ninfo=None,
**kwargs)
Add a Node object to the graph. |
source code
|
|
|
|
|
|
|
useEdges(self,
**kwargs)
Pull some edges from the DbStore backing this subgraph into the
actual visgraph.graphcore.Graph instance so path traversal is
possible. |
source code
|
|
|
|
expandNode(self,
nid,
maxdepth=1)
Add *all* the edges (and adjacent nodes) by traversing this nodes
edges to the specified depth... |
source code
|
|
|
Inherited from DbGraphStore:
buildSubGraph,
delEdge,
delNode,
delNodeInfo,
getEdgeInfo,
getNodeInfo,
getNodeProps,
getRefsFrom,
getRefsTo,
searchNodes,
setEdgeInfo,
setNodeInfo
Inherited from graphcore.Graph:
getClusterGraphs,
getEdge,
getEdges,
getMeta,
getNode,
getNodes,
hasNode,
pathSearch,
pathSearchFrom,
pathSearchOne,
setMeta,
wipeGraph
|