Update 42NA9 to reflect code updates#463
Conversation
Hunterness
added
DO NOT MERGE
team-cypher-operations
renetapopova
left a comment
renetapopova
left a comment
There was a problem hiding this comment.
Hey @Hunterness, thanks for the examples. Really useful. I left some editorial comments, mainly related to consistency with the rest of the errors.
renetapopova
left a comment
renetapopova
left a comment
There was a problem hiding this comment.
Should be good now. Could you please take a final look?
There was a problem hiding this comment.
Looks good, but I'll keep the DO NOT MERGE label and it not being merged until I merge the code updates for the 42AN9 code (one of my other tasks came back and took priority so I didn't get around to finishing the coding side yet :( hopefully next week 🤞)
Since 42AN9 is an existing code in use I think we should keep the existing message until it's actually changed
|
The changes were merged into 2026.03, so I guess this should be good to do? @renetapopova |
We're allowing CALL procedure both together with SHOW/TERMINATE commands and multiple CALL clauses together so 42NA9 is out of date and should be updated. Also add examples for both that and 42N17.
Co-authored-by: Reneta Popova <reneta.popova@neo4j.com>
renetapopova
force-pushed
the
COPS-465-update-gql-42na9
branch
from
d08c296 to
269079f
Compare
|
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
3 participants
We're allowing CALL procedure both together with (some of the) SHOW/TERMINATE commands and multiple CALL clauses together so 42NA9 is out of date and should be updated.
Also add examples for both that and 42N17.
The updates to behaviour have not yet been merged (PR), so neither should this PR.