Skip to content

Local callables status codes - #539

Open
hvub wants to merge 4 commits into
neo4j:devfrom
hvub:local-callables-status-codes
Open

hvub wants to merge 4 commits into
neo4j:devfrom
hvub:local-callables-status-codes

Conversation

@hvub

@hvub hvub commented Sep 25, 2026

Copy link
Copy Markdown
Contributor

Builds on #537.

@renetapopova renetapopova self-assigned this Sep 25, 2026
@renetapopova

Copy link
Copy Markdown
Collaborator

Builds on #537.

Why?

@JoelBergstrand JoelBergstrand self-assigned this Sep 29, 2026
@hvub
hvub force-pushed the local-callables-status-codes branch from 3dec7d0 to e48c5ca Compare September 29, 2026 08:34
@renetapopova

Copy link
Copy Markdown
Collaborator

I think it's fine to merge this one and open a separate PR with the other codes.

@renetapopova

Copy link
Copy Markdown
Collaborator

I think it's fine to merge this one and open a separate PR with the other codes.

Sorry, I meant the other PR.

@hvub
hvub force-pushed the local-callables-status-codes branch from e48c5ca to b1f7119 Compare September 30, 2026 13:25
Comment thread modules/ROOT/pages/errors/gql-errors/42NAH.adoc
Comment thread modules/ROOT/pages/errors/gql-errors/42NAH.adoc Outdated
Comment thread modules/ROOT/pages/errors/gql-errors/42NAI.adoc
Comment thread modules/ROOT/pages/errors/gql-errors/42NAJ.adoc Outdated
Comment thread modules/ROOT/pages/errors/gql-errors/42NAH.adoc

@renetapopova renetapopova left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I have pushed some editorial updates and added some comments on how to improve the status descriptions.

= 42NAI

== Status description
error: syntax error or access rule violation - missing return column. Return column `{ <<variable>> }` is missing to match output signature of local procedure `{ <<proc>> }`.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

How about something like:

Suggested change
error: syntax error or access rule violation - missing return column. Return column `{ <<variable>> }` is missing to match output signature of local procedure `{ <<proc>> }`.
error: syntax error or access rule violation - missing return column. Return column `{ <<variable>> }` is required to match the output signature of local procedure `{ <<proc>> }`.

= 42NAH

== Status description
error: syntax error or access rule violation - return column error. Return column `{ <<variable>> }` does not match output signature of local procedure `{ <<proc>> }`.

Copy link
Copy Markdown
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 - return column error. Return column `{ <<variable>> }` does not match output signature of local procedure `{ <<proc>> }`.
error: syntax error or access rule violation - return column error. Return column `{ <<variable>> }` does not match the output signature of local procedure `{ <<proc>> }`.

= 42NAG

== Status description
error: syntax error or access rule violation - not supported local function definition. USE clause is not supported in local function definitions.

Copy link
Copy Markdown
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 - not supported local function definition. USE clause is not supported in local function definitions.
error: syntax error or access rule violation - not supported local function definition. The USE clause is not supported in local function definitions.

= 42NAF

== Status description
error: syntax error or access rule violation - not supported local procedure definition. USE clause is not supported in local procedure definitions.

Copy link
Copy Markdown
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 - not supported local procedure definition. USE clause is not supported in local procedure definitions.
error: syntax error or access rule violation - not supported local procedure definition. The USE clause is not supported in local procedure definitions.

= 42NAJ

== Status description
error: syntax error or access rule violation - not supported local procedure output type. `{ <<valueType>> }` is not supported as local procedure output type. Adjust the type of output field `{ <<variable>> }` of local procedure `{ <<proc>> }`.

Copy link
Copy Markdown
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 - not supported local procedure output type. `{ <<valueType>> }` is not supported as local procedure output type. Adjust the type of output field `{ <<variable>> }` of local procedure `{ <<proc>> }`.
error: syntax error or access rule violation - not supported local procedure output type. `{ <<valueType>> }` is not supported as a local procedure output type. Adjust the type of output field `{ <<variable>> }` of local procedure `{ <<proc>> }`.

= 42NAK

== Status description
error: syntax error or access rule violation - not supported local function return type. `{ <<valueType>> }` is not supported as local function return type. Adjust the return type of local function `{ <<fun>> }`.

Copy link
Copy Markdown
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 - not supported local function return type. `{ <<valueType>> }` is not supported as local function return type. Adjust the return type of local function `{ <<fun>> }`.
error: syntax error or access rule violation - not supported local function return type. `{ <<valueType>> }` is not supported as a local function return type. Adjust the return type of local function `{ <<fun>> }`.

= 42NAL

== Status description
error: syntax error or access rule violation - not supported local callable parameter type. `{ <<valueType>> }` is not supported as local callable parameter type. Adjust the type of parameter `{ <<variable>> }` of local callable `{ <<procFun>> }`.

Copy link
Copy Markdown
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 - not supported local callable parameter type. `{ <<valueType>> }` is not supported as local callable parameter type. Adjust the type of parameter `{ <<variable>> }` of local callable `{ <<procFun>> }`.
error: syntax error or access rule violation - not supported local callable parameter type. `{ <<valueType>> }` is not supported as a local callable parameter type. Adjust the type of parameter `{ <<variable>> }` of local callable `{ <<procFun>> }`.

= 42NAO

== Status description
error: syntax error or access rule violation - invalid use of CALL IN TRANSACTIONS and local callables. 'CALL { ... } IN TRANSACTIONS' is not supported in combination with 'DEFINE'.

Copy link
Copy Markdown
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 CALL IN TRANSACTIONS and local callables. 'CALL { ... } IN TRANSACTIONS' is not supported in combination with 'DEFINE'.
error: syntax error or access rule violation - invalid use of CALL IN TRANSACTIONS and local callables. CALL { ... } IN TRANSACTIONS is not supported in combination with DEFINE.

@renetapopova
renetapopova force-pushed the local-callables-status-codes branch from 5d373b3 to dca744c Compare October 7, 2026 14:15
@neo4j-docops-agent

Copy link
Copy Markdown
Collaborator

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

New pages:

Updated pages:

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.

4 participants