[GH-ISSUE #3246] SQL syntax error without prompt #1187

New issue

Closed

opened 2026-03-07 21:00:47 +03:00 by kerem · 0 comments

kerem commented

2026-03-07 21:00:47 +03:00

Owner

Originally created by @mail200 on GitHub (Feb 7, 2025).
Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/3246

When creating PROCEDURE in Oracle database, there are incorrect table names in SQL,
For example, the table P_DUXY12.Z-PCDWOPENSO_20250206 does not actually exist, but when executing SQL, there is no prompt that the table does not exist, and it is executed normally instead.
Is there any way to indicate an error?

SQL statement
CREATE OR REPLACE PROCEDURE P_DUXY12.PRC_TEST_20250206(exitcode OUT NUMBER) IS
BEGIN
exitcode := -20099;

insert into P_DUXY12.Z_PCDW_OPENSO_20250206
(scenario_id,
vbeln,
agree,
ship_to_country)
select scenario_id,
vbeln,
agree,
ship_to_country
from P_DUXY12.Z_PCDW_OPENSO;
commit;
exitcode := 0;
EXCEPTION
WHEN OTHERS THEN
exitcode := -1;
RAISE;
END PRC_TEST_20250206;

Originally created by @mail200 on GitHub (Feb 7, 2025). Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/3246 When creating PROCEDURE in Oracle database, there are incorrect table names in SQL, For example, the table P_DUXY12.Z-PCDWOPENSO_20250206 does not actually exist, but when executing SQL, there is no prompt that the table does not exist, and it is executed normally instead. Is there any way to indicate an error? SQL statement CREATE OR REPLACE PROCEDURE P_DUXY12.PRC_TEST_20250206(exitcode OUT NUMBER) IS BEGIN exitcode := -20099; insert into P_DUXY12.Z_PCDW_OPENSO_20250206 (scenario_id, vbeln, agree, ship_to_country) select scenario_id, vbeln, agree, ship_to_country from P_DUXY12.Z_PCDW_OPENSO; commit; exitcode := 0; EXCEPTION WHEN OTHERS THEN exitcode := -1; RAISE; END PRC_TEST_20250206;

Rows
Columns