Skip to content

Conversation

@dogofbrian
Copy link

New error codes (and one message update) for path mode semantic checking

@neo4j-docops-agent
Copy link
Collaborator

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

New pages:

Updated pages:

@arnefischereit arnefischereit added the team-cypher-planner Changes that Team Cypher Planner should look into label Oct 27, 2025
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.

Thanks, @dogofbrian. I added some comments.

@@ -1,7 +1,7 @@
= 42I39
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
= 42I39
:page-role: new-2025.11
= 42I39

@@ -0,0 +1,11 @@
= 42N60
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
= 42N60
:page-role: new-2025.11
= 42N60

@@ -0,0 +1,11 @@
= 42N61
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
= 42N61
:page-role: new-2025.11
= 42N61


== Status description
error: syntax error or access rule violation - invalid use of shortest path function. Mixing the `{ <<fun>> }` function with path selectors or explicit match modes is not allowed.
error: syntax error or access rule violation - invalid use of shortest path function. Mixing the `{ <<fun>> }` function with path selectors, explicit match modes or explicit path modes is not allowed.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
error: syntax error or access rule violation - invalid use of shortest path function. Mixing the `{ <<fun>> }` function with path selectors, explicit match modes or explicit path modes is not allowed.
error: syntax error or access rule violation - invalid use of shortest path function. Mixing the `{ <<fun>> }` function with path selectors, explicit match modes, or explicit path modes is not allowed.

= 42N60

== Status description
error: syntax error or access rule violation - unsupported combination of match mode and path mode. REPEATABLE ELEMENTS with `{ <<pathMode>> }` path mode is not supported.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why is REPEATABLE ELEMENTS capitalized?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Could we also add an explanation/ example scenario for each of the errors? See 22N71, 22N69, 22NAB, 42I64, and many more for inspiration.

= 42N61

== Status description
error: syntax error or access rule violation - unsupported mixing of different path modes. Mixing `{ <<pathModeList>> }` in the same graph pattern is not supported. Split the pattern into separate MATCH clauses instead.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
error: syntax error or access rule violation - unsupported mixing of different path modes. Mixing `{ <<pathModeList>> }` in the same graph pattern is not supported. Split the pattern into separate MATCH clauses instead.
error: syntax error or access rule violation - unsupported mixing of different path modes. Mixing `{ <<pathModeList>> }` in the same graph pattern is not supported. Split the pattern into separate `MATCH` clauses instead.

@renetapopova renetapopova self-assigned this Oct 28, 2025
@blouerat blouerat self-assigned this Oct 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

2025.11 team-cypher-planner Changes that Team Cypher Planner should look into

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants