imbajin commented on code in PR #499:
URL: https://github.com/apache/hugegraph-doc/pull/499#discussion_r4228568384
##########
content/en/docs/language/cypher-compatibility.md:
##########
@@ -0,0 +1,154 @@
+---
+title: "Cypher Compatibility"
+linkTitle: "Cypher Compatibility"
+weight: 3
+---
+
+### Scope
+
+**The verification results below describe `master`, not a released HugeGraph
version.** HugeGraph 1.7.0 exposes exactly two
+request forms on `/graphspaces/{graphspace}/graphs/{graph}/cypher`: `GET
?cypher=<URL-encoded statement>`
+and `POST application/json` with a raw Cypher body. Releases before 1.7.0
expose the same two forms under
+`/graphs/{graph}/cypher`. Released versions accept no bound parameters, and a
+statement that references `$param` returns no rows rather than failing — see
Review Comment:
⚠️ Important: This says every statement referencing `$param` returns no
rows, but released versions inline a missing binding as `null`; row behavior
then depends on the expression. For example, `RETURN $value AS value` can
return a row containing `null`, while the documented equality predicate returns
no rows. Please scope the no-rows claim to the predicate case and align the
repeated EN/CN statements. Evidence: `CypherOpProcessor` at 1.7.0 configures
`inline_parameters` and parses the statement without missing-binding
validation; the merged `CypherApiTest` at 5039e5b verifies that `RETURN $value
AS value` with a null value returns a row.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
