From c0df9c721b85a4eadc643638d7c4b304829d488a Mon Sep 17 00:00:00 2001 From: Andreas Kollegger Date: Fri, 9 Dec 2011 12:13:19 -0500 Subject: [PATCH] slight elaboration about neo4j model during intro material --- src/docbkx/tutorial/neo4j.xml | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/src/docbkx/tutorial/neo4j.xml b/src/docbkx/tutorial/neo4j.xml index a7be8aec8..d4690abbd 100644 --- a/src/docbkx/tutorial/neo4j.xml +++ b/src/docbkx/tutorial/neo4j.xml @@ -8,7 +8,10 @@ First we read up about graph databases, in particular our chosen one, Neo4j. The Neo4j data model consists of nodes and relationships, both of which can have key/value-style - properties. Relationships are first-class citizens in Neo4j, meaning we can link together nodes + properties. What does that mean, exactly? Nodes are the graph database name for records, + with property keys instead of column names. That's normal enough. Relationships are the special part. + In Neo4j, relationships are first-class citizens, meaning they are more than a simple foreign-key + reference to another record, relationships carry information. So we can link together nodes into semantically rich networks. This really appealed to us. Then we found that we were also able to index nodes and relationships by {key, value} pairs. We also found that we could traverse relationships both imperatively using @@ -27,9 +30,9 @@ Something to keep in mind later. - We started out by doing some prototyping with the Neo4j core API to get a feeling for how it works. And also - to see, what the domain might look like when it's saved in the graph database. After adding the Maven - dependency for Neo4j, we were ready to go. + We started out by doing some prototyping with the Neo4j core API to get a feeling for how it works. And + also, to see what the domain might look like when it's saved in the graph database. After adding the Maven + dependency for Neo4j, we were ready to go.