Issue:
Run Statement (Ctrl+Enter/F9) may execute a malformed statement by dropping an invalid WHERE part, instead of raising syntax error.
Repro:
-
SQL Worksheet, attached connection.
-
Run this (cursor inside statement, no text selection):
SELECT sys_context('USERENV', 'DB_NAME') AS db_name, last_login, account_status
FROM DBA_USERS
WHERE username = 'XYZ;
Expected:
Fail with syntax error (e.g. quoted string not properly terminated).
Actual:
Statement may execute as if WHERE clause is removed.
Note:
If the same malformed SQL is explicitly selected and run, error is shown correctly.
Impact:
Risk of unintended broad query results.
Request:
Please enforce strict parsing for Run Statement (or add a setting) so malformed SQL always fails and is never auto-truncated.