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
Constants isc_lock_conflict / isc_eds_statement not recognized in PSQL [CORE3349] #3715
Comments
Commented by: @dyemanov "when gdscode eds_statement do", i.e. you must omit the "isc_" prefix. |
Commented by: @hvlad It seems as undocumented feature since IB6 :) And it was my mistake in README.execute_statement2 - Sergey just used my examples with full names of errors. |
Commented by: Sergey Mereutsa (green_dq) Changed to documentation error - constants should be used without "isc_" prefix. |
Modified by: Sergey Mereutsa (green_dq)Component: Documentation [ 10011 ] Component: API / Client Library [ 10040 ] => |
Modified by: @hvladassignee: Vlad Khorsun [ hvlad ] |
Commented by: @hvlad Fixed examples at README.execute_statement2 |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: Cannot be tested Test Details: Issue of this ticket is about documentation rather than FB behaviour. |
Submitted by: Sergey Mereutsa (green_dq)
Try to compile the following code:
SET TERM ^ ;
create procedure proc_eds
as
declare variable i integer;
begin
execute statement ('select 1 from rdb$database') into :i;
when gdscode isc_eds_statement do
begin
exit;
end
end
^
SET TERM ; ^
You`ll got the following error:
Statement failed, SQLSTATE = HY000
invalid request BLR at offset 89
-status code isc_eds_statement unknown
The same behavior with isc_lock_conflict constant.
Commits: 9f5a439 f1ddbd3
====== Test Details ======
Issue of this ticket is about documentation rather than FB behaviour.
The text was updated successfully, but these errors were encountered: