You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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.
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!
The text was updated successfully, but these errors were encountered: