| = The Neo4j GraphGist Console = | |
| This is a sample GraphGist explaining some of the base concepts of sharing graphs using http://docs.neo4j.org/chunked/milestone/cypher-query-lang.html[the Cypher query language]. | |
| [source,cypher] | |
| ---- | |
| CREATE ({name:'you'})-[:SEE]->({name:'This GraphGist'})-[:FORK_ON_GITHUB]->(your_gistfile{name:'Your Gist'}) | |
| CREATE (your_gistfile)-[:INSERT_ID_HERE]->({name:'Your GraphGist'}) | |
| ---- |
The Royal families generaly have long histories and are often closely related. This citation from wikipedia can give you better idea:
Maternally, Nicholas was the nephew of several monarchs, including King Frederick VIII of Denmark, Queen Alexandra of the United Kingdom (queen consort of King Edward VII), and King George I of Greece. Nicholas, his wife, Alexandra, and Kaiser Wilhelm II of Germany were all first cousins of King George V of the United Kingdom. Nicholas was also a first cousin of both King Haakon VII and Queen Maud of Norway, as well as King Constantine I of Greece. While not first cousins, Nicholas and Kaiser Wilhelm II were second cousins, once removed, as each descended from King Frederick William III of Prussia, as well as third cousins, as they were both great-great-grandsons of Emperor Paul I of Russia.
The rulers of Great Britain, Germany and Russia at the beginning of World War I were actually cousins
| = Product Catalog | |
| Aravind R. Yarram <yaravind@gmail.com> | |
| v1.0, 17-Sep-2013 | |
| :neo4j-version: 2.0.0-RC1 | |
| :author: Aravind R. Yarram | |
| :twitter: funpluscharity | |
| == Domain | |
| A product catalog is a collection of products, their categories, manufacturers with their pricing information. Products can be sold separately, included in one or more catalogs or used as substitute products |
| = Merge Examples = | |
| :neo4j-version: 2.0.0-RC1 | |
| :author: Andrés Taylor | |
| :twitter: @andres_taylor | |
| :tags: domain:example | |
| //setup | |
| [source,cypher] | |
| ---- |
| = Why JIRA should use Neo4j, really | |
| == Introduction | |
| There are few developers in the world that have never used an issue tracker. But there are even fewer developers who have ever used an issue tracker which uses a graph database. This is a shame because issue tracking really maps much better onto a graph database, than it does onto a relational database. Proof of that is the https://developer.atlassian.com/download/attachments/4227160/JIRA61_db_schema.pdf?api=v2[JIRA database schema]. | |
| Now obviously, the example below does not have all of the features that a tool like JIRA provides. But it is only a proof of concept, you could map every feature of JIRA into a Neo4J database. What I've done below, is take out some of the core functionalities and implement those. | |
| == The data set |
| = People, books and cities | |
| == Modeling the Graph | |
| Let's take a look at the domain model: | |
| image::http://i.imgur.com/TJCNW0b.jpg?1[] | |
| //setup | |
| //hide | |
| [source, cypher] |
| = Untying the Graph Database Import Knot = | |
| This Graphgist accompanies http://blog.bruggen.com/2013/12/untying-graph-database-import-knot.html[my blogpost of December 6th, 2013] which tries to explain the different types of questions that people should be asking themselves when thinking about importing data into http://www.neo4j.org[neo4j], and the tools that can contribute to finding the most optimal import strategy for your specific use case. | |
| //setup | |
| //hide | |
| [source,cypher] | |
| ---- | |
| create (n1:Tool {id:'1',name:'Spreadsheets'}), | |
| (n2:Tool {id:'2',name:'Cypher Statements'}), |
