Errata

Dear Authors,

I am writing to provide feedback regarding a specific example in your book, "Building Knowledge Graphs: A Practitioner’s Guide." The example in question is Example 5-5, which features a Cypher query integrating SQL results with Neo4j graph operations.

The query in the example utilizes the `MATCH (row)` construct, where `row` represents the result of an SQL query obtained via `apoc.load.jdbcParams`. In standard practice of Cypher query language for Neo4j, the `MATCH` clause is primarily used to identify and match nodes and relationships within the graph based on specific patterns or criteria. However, using `MATCH (row)` directly, where `row` is a row of SQL results, seems to be inconsistent with these standard practices.

In Cypher, a row from an SQL result set is not directly equivalent to a node or relationship in the Neo4j graph. Therefore, using `MATCH (row)` as presented in the example does not align with the typical usage and functionality of the Cypher language in Neo4j.

It appears that there might be an error or oversight in this specific example. For clarity and accuracy, it might be beneficial to review and potentially revise this example. A more conventional approach would involve extracting specific fields from the SQL result `row` and then using these fields to match or create nodes and relationships in Neo4j. For instance:

```cypher
CALL apoc.load.jdbcParams("jdbc-url", sql, params) YIELD row
MATCH (p:Person) WHERE p.firstName = row.firstname AND p.lastName = row.lastname
// Further logic...
```
I am not familiar with Cypher, but
this approach aligns more closely with Cypher's standard practices and the functionality of integrating SQL results with Neo4j operations.

Thank you for your attention to this matter, and for your dedication to providing accurate and valuable resources for the community.

Best regards

Note from the Author or Editor:
The errata is accurate. We missed out

MATCH (:Person (firstname:row.firstname, lastname:row.lastname))-[:WORKS_FOR*1..3]->(boss:Person)

It is now in the repo and the ebook can be rebuilt.