Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possibility of context SQLCODE variable to be visible (i.e. return the real result) in all PSQL scope [CORE1054] #1473

Closed
firebird-automations opened this issue Dec 14, 2006 · 4 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Maycon Ferraca (ferraca)

Possibility of context SQLCODE variable to be visible (i.e. return the real result) in all PSQL scope, because codes greater that 0 (zero) is not necessarily an error, at least SQLCODE 100.

e.g.
(...)
WHILE (1 = 1) DO
BEGIN
FETCH cur INTO :seq;
IF (SQLCODE = 100) THEN
LEAVE;
END
(...)

I know that exists ROW_COUNT for this case, but SQLCODE at end a cursor must be 100. Right?

Thanks!

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

GDSCODE/SQLCODE work for errors only. It cannot show you warnings or EOS conditions. This is by design, because e.g. SQLCODE 100 is not set internally by the engine -- it's done at upper layers.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 11391 ] => Firebird [ 15416 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Won't Fix [ 2 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

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

No branches or pull requests

1 participant