Skip to content

Update 42NA9 to reflect code updates#463

Open
Hunterness wants to merge 6 commits intoneo4j:devfrom
Hunterness:COPS-465-update-gql-42na9
Open

Update 42NA9 to reflect code updates#463
Hunterness wants to merge 6 commits intoneo4j:devfrom
Hunterness:COPS-465-update-gql-42na9

Conversation

@Hunterness
Copy link
Contributor

@Hunterness Hunterness commented Feb 12, 2026

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, so neither should this PR.

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.
@Hunterness Hunterness added DO NOT MERGE team-cypher-operations Cypher operations should review this labels Feb 12, 2026
Copy link
Collaborator

@renetapopova renetapopova left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @Hunterness, thanks for the examples. Really useful. I left some editorial comments, mainly related to consistency with the rest of the errors.

Hunterness and others added 3 commits February 12, 2026 16:55
@renetapopova renetapopova self-requested a review February 20, 2026 10:54
@neo4j-docops-agent
Copy link
Collaborator

This PR includes documentation updates
View the updated docs at https://neo4j-docs-status-codes-463.surge.sh

Updated pages:

Copy link
Collaborator

@renetapopova renetapopova left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be good now. Could you please take a final look?

Copy link
Contributor Author

@Hunterness Hunterness left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

DO NOT MERGE team-cypher-operations Cypher operations should review this

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants