The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".
The following errata were submitted by our customers and approved as valid errors by the author or editor.
Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
Version |
Location |
Description |
Submitted By |
Date submitted |
Date corrected |
|
Page vii
2nd paragrqaph, l |
"what to with it." should read "what to do with it."
This has been fixed in the project Git repository.
Note from the Author or Editor: Thanks for the feedback, this is correct in the git repo now as you stated.
|
Jim Webber |
Jul 03, 2023 |
|
|
Page Example 5-5
MATCH(row) |
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.
|
Anonymous |
Jan 16, 2024 |
|
|
Page viii
2nd paragraph |
". . . software engineers, system architects, and techincal managers . . ." should be ". . . software engineers, system architects, and technical managers . . ."
Note from the Author or Editor: Errata is good, and has been fixed in repo.
|
James Deegan |
Jan 25, 2024 |
|
|
Page 74
2nd paragraph |
Verb used twice by mistake: "... why not use use APOC ... ".
Note from the Author or Editor: Confirmed, thanks for the feedback.
|
Anonymous |
Jul 29, 2023 |
|
|
Page 74
2nd paragraph |
"an" instead of "a" in the following case:
- Current version: "... make calls into a SQL ..."
- Change it to: "... make calls into an SQL ..."
Note from the Author or Editor: Tricky one this. It depends on whether you read this as "a SEQUEL" database or "an ESS-QL" database.
Nonetheless, I've accepted the change - thanks for the feedback.
|
Anonymous |
Jul 29, 2023 |
|
|
Page 94
1st paragraph |
Introduce a comma:
- "As in Chapter 3 Neo4j has been ..." to
- "As in Chapter 3, Neo4j has been ...".
Note from the Author or Editor: Confirmed - thanks for taking the time to give us feedback.
|
Anonymous |
Aug 02, 2023 |
|