Neo4j:Basics - Introduction - Revision history

40166222: 40166222 moved page Neo4j:Basics - MATCH to Neo4j:Basics - Introduction without leaving a redirect

2018-10-15T10:28:35Z

40166222 moved page Neo4j:Basics - MATCH to Neo4j:Basics - Introduction without leaving a redirect

← Older revision	Revision as of 10:28, 15 October 2018
(No difference)

40166222 at 15:20, 9 October 2018

2018-10-09T15:20:57Z

← Older revision		Revision as of 15:20, 9 October 2018
Line 63:		Line 63:
	RETURN n;</nowiki></pre>		RETURN n;</nowiki></pre>
	</div>		</div>
	===Query by ~~Atributes~~===		===Query by Attributes===
	<div class="q" data-lang="neo4j">		<div class="q" data-lang="neo4j">
	This query currently gets Zeus' names.		This query currently gets Zeus' names.
Line 70:		Line 70:
	MATCH (g:God {name: "Zeus"})		MATCH (g:God {name: "Zeus"})
	RETURN g.name, g.greek;</nowiki></pre>		RETURN g.name, g.greek;</nowiki></pre>
	<pre class="ans"><nowiki>MATCH (g:God {name: "Zeus"}) RETURN g.name, g.greek;</nowiki></pre>		<pre class="ans"><nowiki>MATCH (g:God {name:"Zeus"}) RETURN g.name, g.greek;</nowiki></pre>
	</div>		</div>
	==='''IN'''===		==='''IN'''===

40166222: /* WHERE */

2018-10-03T14:10:13Z

WHERE

← Older revision		Revision as of 14:10, 3 October 2018
Line 45:		Line 45:
	WHERE n:God AND n.name = 'Hera'		WHERE n:God AND n.name = 'Hera'
	RETURN n;</nowiki></pre>		RETURN n;</nowiki></pre>
	<pre class="ans"><nowiki>MATCH (g) WHERE g:God AND g.name = 'Zeus' RETURN g; </nowiki></pre>		<pre class="ans"><nowiki>MATCH (n) WHERE n:God AND n.name = 'Zeus' RETURN n; </nowiki></pre>
	</div>		</div>
	===Combining '''MATCH''' and '''WHERE'''===		===Combining '''MATCH''' and '''WHERE'''===

40166222: /* WHERE */

2018-10-02T21:32:32Z

WHERE

← Older revision		Revision as of 21:32, 2 October 2018
Line 43:		Line 43:
	<pre class="def"><nowiki>		<pre class="def"><nowiki>
	MATCH (n)		MATCH (n)
	WHERE n:God AND n.name = '~~Zeus~~'		WHERE n:God AND n.name = 'Hera'
	RETURN n;</nowiki></pre>		RETURN n;</nowiki></pre>
	<pre class="ans"><nowiki>MATCH (g) WHERE g:God AND g.name = 'Zeus' RETURN g; </nowiki></pre>		<pre class="ans"><nowiki>MATCH (g) WHERE g:God AND g.name = 'Zeus' RETURN g; </nowiki></pre>

40166222: /* Introduction to Graphs and the 'Graph Property Model' */

2018-10-02T17:18:18Z

Introduction to Graphs and the 'Graph Property Model'

← Older revision		Revision as of 17:18, 2 October 2018
Line 5:		Line 5:

	==Introduction to Graphs and the 'Graph Property Model'==		==Introduction to Graphs and the 'Graph Property Model'==
	You've likely heard of graphs before. In mathematics a graph is the term for a set of vertices and edges, here it is a collection of nodes and relationships respectively.		You've likely heard of graphs before. In mathematics a graph is the term for a set of vertices and edges, here it is a collection of nodes and relationships respectively. In Neo4j graphs follow the "'''Property Graph Model'''". <br />

	~~In Neo4j graphs follow the "Property Graph Model". A~~ property is just a key-value pair, such as <code>name: 'Alice'</code>, <code>age: 27</code>~~, pet_dogs~~. Users who have used document-oriented databases such as [https://no.sqlzoo.net/wiki/Main_Page MongoDB] or who have used JavaScript Object Notation (JSON) will be familiar with this concept already.		Here a property is just a key-value pair, such as <code>name: 'Alice'</code>, or <code>age: 27</code>. Users who have used document-oriented databases such as [https://no.sqlzoo.net/wiki/Main_Page MongoDB] or who have used JavaScript Object Notation (JSON) will be familiar with this concept already.<br/>

	A node is a simple entity that contains ~~any amount of properties.~~ A node representing a person might include things like their name, date of birth, or hometown, etc.		A node is a simple entity that contains A node representing a person might include things like their name, date of birth, or hometown, etc. <br />
	As well as containing properties, nodes can be labelled as belonging to a certain group for query purposes. For example, in a database of celebrities <code>Frank Ocean</code> could be labelled as an <code>:Musician</code>. There's no limit to the amount of labels that can apply to a node, the celebrity <code>Hugh Laurie</code> could be simultaneously labelled as an <code>:Actor</code>, <code>:Musician</code>, and <code>:Author</code>.		As well as containing properties, nodes can be labelled as belonging to a certain group for query purposes. For example, in a database of celebrities <code>Frank Ocean</code> could be labelled as an <code>:Musician</code>. There's no limit to the amount of labels that can apply to a node, the celebrity <code>Hugh Laurie</code> could be simultaneously labelled as an <code>:Actor</code>, <code>:Musician</code>, and <code>:Author</code>. <br/>

	In the property graph model, a relationship is a connection between exactly two nodes, though there's not limit to the amount of relationships a node made have. A relationship always has both a '''name''' and a '''direction''' (start node and end node), and like a node it can also have properties. Bidirectional relationships are a little trickier, and are out-width the scope of this tutorial: [[Neo4j:Modelling Bidirectional Relationships \| Modelling Bidirectional Relationships]]		In the property graph model, a relationship is a connection between exactly two nodes, though there's not limit to the amount of relationships a node made have. A relationship always has both a '''name''' and a '''direction''' (start node and end node), and like a node it can also have properties. Bidirectional relationships are a little trickier, and are out-width the scope of this tutorial: [[Neo4j:Modelling Bidirectional Relationships \| Modelling Bidirectional Relationships]] <br/>

	This remainder of this tutorial will use the [https://neo4j.com/developer/cypher-query-language/ Cypher] query language (CQL) to introduce some basic concepts.		This remainder of this tutorial will use the [https://neo4j.com/developer/cypher-query-language/ Cypher] query language (CQL) to introduce some basic concepts.

40166222: Fix misspelled words, Barry Manilow -> Frank Ocean (don't listen to william's music suggestions)

2018-10-02T17:03:16Z

Fix misspelled words, Barry Manilow -> Frank Ocean (don't listen to william's music suggestions)

← Older revision		Revision as of 17:03, 2 October 2018
Line 9:		Line 9:
	In Neo4j graphs follow the "Property Graph Model". A property is just a key-value pair, such as <code>name: 'Alice'</code>, <code>age: 27</code>, pet_dogs. Users who have used document-oriented databases such as [https://no.sqlzoo.net/wiki/Main_Page MongoDB] or who have used JavaScript Object Notation (JSON) will be familiar with this concept already.		In Neo4j graphs follow the "Property Graph Model". A property is just a key-value pair, such as <code>name: 'Alice'</code>, <code>age: 27</code>, pet_dogs. Users who have used document-oriented databases such as [https://no.sqlzoo.net/wiki/Main_Page MongoDB] or who have used JavaScript Object Notation (JSON) will be familiar with this concept already.

	A node is a simple entity that contains any amount of properties. A node representing a person might include things like their name, date of birth, or hometown etc.		A node is a simple entity that contains any amount of properties. A node representing a person might include things like their name, date of birth, or hometown, etc.
	As well as containing properties, nodes can be ~~labeled~~ as belonging to a certain group for query purposes. For example, in a database of celebrities <code>~~Barry Manilow~~</code> could be ~~labeled~~ as an <code>:Musician</code>. There's no limit to the amount of labels that can apply to a node, the celebrity <code>Hugh Laurie</code> could be simultaneously ~~labeled~~ as an <code>:Actor</code>, <code>:Musician</code>, and <code>:Author</code>.		As well as containing properties, nodes can be labelled as belonging to a certain group for query purposes. For example, in a database of celebrities <code>Frank Ocean</code> could be labelled as an <code>:Musician</code>. There's no limit to the amount of labels that can apply to a node, the celebrity <code>Hugh Laurie</code> could be simultaneously labelled as an <code>:Actor</code>, <code>:Musician</code>, and <code>:Author</code>.

	In the property graph model, a relationship is a connection between exactly two nodes, though there's not limit to the amount of relationships a node made have. A relationship always has both a '''name''' and a '''direction''' (start node and end node), and like a node it can also have properties. Bidirectional relationships are a little trickier, and are out-width the scope of this tutorial: [[Neo4j:Modelling Bidirectional Relationships \| Modelling Bidirectional Relationships]]		In the property graph model, a relationship is a connection between exactly two nodes, though there's not limit to the amount of relationships a node made have. A relationship always has both a '''name''' and a '''direction''' (start node and end node), and like a node it can also have properties. Bidirectional relationships are a little trickier, and are out-width the scope of this tutorial: [[Neo4j:Modelling Bidirectional Relationships \| Modelling Bidirectional Relationships]]

	This remainder of this tutorial will use the [https://neo4j.com/developer/cypher-query-language/ Cypher] query language (CQL) to introduce some basic concepts.		This remainder of this tutorial will use the [https://neo4j.com/developer/cypher-query-language/ Cypher] query language (CQL) to introduce some basic concepts.

	=='''RETURN'''==		=='''RETURN'''==

40166222: Remove trailing newlines

2018-10-02T17:00:08Z

Remove trailing newlines

← Older revision		Revision as of 17:00, 2 October 2018
Line 33:		Line 33:
	<pre class="def"><nowiki>		<pre class="def"><nowiki>
	MATCH (n)		MATCH (n)
	RETURN n;		RETURN n;</nowiki></pre>
	</nowiki></pre>
	</div>		</div>
	=='''WHERE'''==		=='''WHERE'''==
Line 45:		Line 44:
	MATCH (n)		MATCH (n)
	WHERE n:God AND n.name = 'Zeus'		WHERE n:God AND n.name = 'Zeus'
	RETURN n;		RETURN n;</nowiki></pre>
	</nowiki></pre>
	<pre class="ans"><nowiki>MATCH (g) WHERE g:God AND g.name = 'Zeus' RETURN g; </nowiki></pre>		<pre class="ans"><nowiki>MATCH (g) WHERE g:God AND g.name = 'Zeus' RETURN g; </nowiki></pre>
	</div>		</div>
Line 54:		Line 52:
	<pre class="def"><nowiki>		<pre class="def"><nowiki>
	MATCH (g:God {name: 'Zeus'})		MATCH (g:God {name: 'Zeus'})
	RETURN g;		RETURN g;</nowiki></pre>
	</nowiki></pre>
	</div>		</div>
	===Query by ID===		===Query by ID===
Line 64:		Line 61:
	MATCH (n)		MATCH (n)
	WHERE id(n) = 2		WHERE id(n) = 2
	RETURN n;		RETURN n;</nowiki></pre>
	</nowiki></pre>
	</div>		</div>
	===Query by Atributes===		===Query by Atributes===
Line 83:		Line 79:
	MATCH (g:God)		MATCH (g:God)
	WHERE g.name IN ['Hera', 'Demeter']		WHERE g.name IN ['Hera', 'Demeter']
	RETURN g.name, g.greek;		RETURN g.name, g.greek;</nowiki></pre>
	</nowiki></pre>
	<pre class="ans"><nowiki>MATCH (g:God) WHERE g.name IN ['Zeus', 'Poseidon', 'Hades'] RETURN g.name, g.greek;</nowiki></pre>		<pre class="ans"><nowiki>MATCH (g:God) WHERE g.name IN ['Zeus', 'Poseidon', 'Hades'] RETURN g.name, g.greek;</nowiki></pre>
	</div>		</div>
Line 94:		Line 89:
	<pre class="def"><nowiki>		<pre class="def"><nowiki>
	MATCH (o:Olympian)		MATCH (o:Olympian)
	RETURN o.name;		RETURN o.name;</nowiki></pre>
	</nowiki></pre>
	<pre class="ans"><nowiki>MATCH (o:Olympian) WHERE NOT o.name IN ['Apollo', 'Hestia'] RETURN o.name;</nowiki></pre>		<pre class="ans"><nowiki>MATCH (o:Olympian) WHERE NOT o.name IN ['Apollo', 'Hestia'] RETURN o.name;</nowiki></pre>
	</div>		</div>
Line 106:		Line 100:
	MATCH (o:Olympian)		MATCH (o:Olympian)
	RETURN o.name		RETURN o.name
	ORDER BY o.name;		ORDER BY o.name;</nowiki></pre>
	</nowiki></pre>
	</div>		</div>
	=='''LIMIT'''==		=='''LIMIT'''==
Line 117:		Line 110:
	MATCH (n)		MATCH (n)
	RETURN n		RETURN n
	LIMIT 2;		LIMIT 2;</nowiki></pre>
	</nowiki></pre>
	</div>		</div>
	===Last '''n''' Results.===		===Last '''n''' Results.===
Line 128:		Line 120:
	RETURN n		RETURN n
	ORDER BY n DESC		ORDER BY n DESC
	LIMIT 2;		LIMIT 2;</nowiki></pre>
	</nowiki></pre>
	</div>		</div>

Line 141:		Line 132:
	RETURN n.name		RETURN n.name
	SKIP 10		SKIP 10
	LIMIT 4;		LIMIT 4;</nowiki></pre>
	</nowiki></pre>
	</div>		</div>

	Once comfortable with these questions, move onto [[Neo4j:Basics_-_Relationships\| Neo4j Basics - Relationships]].		Once comfortable with these questions, move onto [[Neo4j:Basics_-_Relationships\| Neo4j Basics - Relationships]].

40166222: /* LIMIT */

2018-06-14T16:23:38Z

LIMIT

← Older revision		Revision as of 16:23, 14 June 2018
Line 110:		Line 110:
	</div>		</div>
	=='''LIMIT'''==		=='''LIMIT'''==
	The '''LIMIT'' clause is used to set a maximum number of results.		The '''LIMIT''' clause is used to set a maximum number of results.
	===First '''n''' Results.===		===First '''n''' Results.===
	<div class="q" data-lang="neo4j">		<div class="q" data-lang="neo4j">
Line 131:		Line 131:
	</nowiki></pre>		</nowiki></pre>
	</div>		</div>

	=='''SKIP'''==		=='''SKIP'''==
	===Skip '''n''' Results. / Find '''n'''th Result.===		===Skip '''n''' Results. / Find '''n'''th Result.===

40166222: /* WHERE */

2018-06-14T16:21:58Z

WHERE

← Older revision		Revision as of 16:21, 14 June 2018
Line 40:		Line 40:
	The '''WHERE''' clause is used to restrict '''MATCH''' patterns.		The '''WHERE''' clause is used to restrict '''MATCH''' patterns.
	<p class="strong">		<p class="strong">
	Find a node, n, with the label ':God' and a name property equal to 'Zeus'.		Find the node(s), n, with the label ':God' and a name property equal to 'Zeus'.
	</p>		</p>
	<pre class="def"><nowiki>		<pre class="def"><nowiki>
Line 98:		Line 98:
	<pre class="ans"><nowiki>MATCH (o:Olympian) WHERE NOT o.name IN ['Apollo', 'Hestia'] RETURN o.name;</nowiki></pre>		<pre class="ans"><nowiki>MATCH (o:Olympian) WHERE NOT o.name IN ['Apollo', 'Hestia'] RETURN o.name;</nowiki></pre>
	</div>		</div>

	=='''ORDER BY'''==		=='''ORDER BY'''==
	<div class="q" data-lang="neo4j">		<div class="q" data-lang="neo4j">

40166222: 40166222 moved page Neo4j:MATCH Basics to Neo4j:Basics - MATCH without leaving a redirect

2018-06-14T16:20:28Z

40166222 moved page Neo4j:MATCH Basics to Neo4j:Basics - MATCH without leaving a redirect

← Older revision	Revision as of 16:20, 14 June 2018
(No difference)