anchor.diff:  
   [source,cypher]
   ----
  -CREATE CONSTRAINT ON (p:Person) ASSERT p.id IS UNIQUE
  +CREATE CONSTRAINT ON (person:Person) ASSERT person.id IS UNIQUE
   ----
   
   [source,cypher]
   ----
  -CREATE CONSTRAINT ON (m:Movie) ASSERT m.id IS UNIQUE
  +CREATE CONSTRAINT ON (movie:Movie) ASSERT movie.id IS UNIQUE
   ----
   
   Now importing the relationships is a matter of finding the nodes and then creating relationships between them.
  
positive.code: LOAD CSV WITH HEADERS FROM "movies.csv" AS csvLine
  MERGE (country:Country {name: csvLine.country})
  CREATE (movie:Movie {id: toInt(csvLine.id), title: csvLine.title, year:toInt(csvLine.year)})
  CREATE (movie)-[:MADE_IN]->(c)
  ----
  
  Lastly, we create the relationships between the persons and the movies.
  Since the relationship is a many to many relationship, one actor can participate in many movies, and one movie has many actors in it.
  
negative.code: ----
  USING PERIODIC COMMIT
  LOAD CSV WITH HEADERS FROM "roles.csv" AS csvLine
  MATCH (person:Person { id: toInt(csvLine.personId)}),(movie:Movie { id: toInt(csvLine.movieId)})
  CREATE (person)-[:PLAYED { role: csvLine.role }]->(movie)
  ----
  
  ////
  Relationships created: 7
  Properties set: 7
  ////
  
  In the query above, we used +USING PERIODIC COMMIT+.
  This hint tells Neo4j that the query might build up inordinate amounts of transaction state, and so needs to be periodically committed.
  