Skip to content

fix: document Cypher parser limitations and correct claims query#79

Merged
sonesuke merged 1 commit intomainfrom
fix/cypher-parser-limitations
Apr 5, 2026
Merged

fix: document Cypher parser limitations and correct claims query#79
sonesuke merged 1 commit intomainfrom
fix/cypher-parser-limitations

Conversation

@sonesuke
Copy link
Copy Markdown
Owner

@sonesuke sonesuke commented Apr 5, 2026

Summary

  • Document 5 known Cypher parser bugs that cause errors or null returns
  • Fix claims retrieval query to use MATCH (c:claims) RETURN c.number, c.text (no ORDER BY, no WHERE)
  • Remove p.claims from "everything" query (always null — claims are child nodes)

Known Cypher Parser Bugs

Pattern Result
ORDER BY toInteger(c.number) c.text returns expression: null
WHERE d.text CONTAINS '...' Parse error
WHERE c.number = '1' Parse error
(p:Patent)-[:claims]->(c:claims) RETURN c.text c.text returns null
p.claims Always null

Workaround

Use direct node match: MATCH (c:claims) RETURN c.number, c.text

🤖 Generated with Claude Code

- Document 5 known Cypher parser bugs (ORDER BY, WHERE, relationship patterns, p.claims, wrong labels)
- Fix claims retrieval to use direct node match MATCH (c:claims) without ORDER BY
- Remove p.claims from "everything" query (always null, claims are child nodes)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@sonesuke sonesuke force-pushed the fix/cypher-parser-limitations branch from e8ac18b to f8cc6d5 Compare April 5, 2026 14:20
@sonesuke sonesuke merged commit 5e465d4 into main Apr 5, 2026
4 checks passed
@sonesuke sonesuke deleted the fix/cypher-parser-limitations branch April 5, 2026 14:29
@sonesuke sonesuke mentioned this pull request Apr 5, 2026
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant