Repository navigation
Conversation
Collaborator
Why? |
hvub
force-pushed
the
local-callables-status-codes
branch
from
September 29, 2026 08:34
3dec7d0 to
e48c5ca
Compare
Collaborator
|
I think it's fine to merge this one and open a separate PR with the other codes. |
Collaborator
Sorry, I meant the other PR. |
hvub
force-pushed
the
local-callables-status-codes
branch
from
September 30, 2026 13:25
e48c5ca to
b1f7119
Compare
renetapopova
reviewed
Oct 7, 2026
renetapopova
left a comment
Collaborator
There was a problem hiding this comment.
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>> }`. |
Collaborator
There was a problem hiding this comment.
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>> }`. |
Collaborator
There was a problem hiding this comment.
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. |
Collaborator
There was a problem hiding this comment.
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. |
Collaborator
There was a problem hiding this comment.
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>> }`. |
Collaborator
There was a problem hiding this comment.
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>> }`. |
Collaborator
There was a problem hiding this comment.
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>> }`. |
Collaborator
There was a problem hiding this comment.
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'. |
Collaborator
There was a problem hiding this comment.
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
force-pushed
the
local-callables-status-codes
branch
from
October 7, 2026 14:15
5d373b3 to
dca744c
Compare
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Builds on #537.