Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You originally asked this question for graph databases (like <a href="http://neo4j.org" rel="noreferrer">Neo4j</a>). That's why I'd like to add some notes.</p> <ol> <li>Graph databases use integrated <a href="http://docs.neo4j.org/chunked/milestone/indexing.html" rel="noreferrer">indexing</a> for nodes (and relationships) so the fast initial lookup for the root nodes of your documents is done via that (external or in graph indexes)</li> <li>Additional in graph indexes for paths (actually trees to the root) can be modelled cleaner that just a key-value lookup)</li> <li>If you model your documents as trees of nodes with properties you can do any simple, and complex CRUD operations (also structural)</li> <li>retrieving all documents of a "type" or "class" can again be done by a index (index root nodes to type) or in graph category nodes</li> <li>you can put those "types or class" category-nodes into a hierarchy (or graph) which then can be edited using the usual graph database API</li> <li>traversing the graph can be done using <a href="http://docs.neo4j.org/chunked/milestone/tutorial-traversal-java-api.html" rel="noreferrer">traversers</a> / integrated graph query language (e.g. <a href="http://docs.neo4j.org/chunked/milestone/cypher-query-lang.html" rel="noreferrer">cypher for Neo4j</a>) </li> <li>Loading hierarchical data can either be done by custom importers or a more general sub-graph importer (e.g. <a href="https://github.com/nigelsmall/py2neo/wiki/GEOFF" rel="noreferrer">GEOFF</a>)</li> </ol>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload