My team recently noticed an interesting bug with statement execution.
We found that sometimes when your cursor is on an SQL block, and you run statement, the text a few rows up gets marked and ran.
I have narrowed down the issue to extra ; and attached an example:
SELECT 1 FROM DUAL;
;
SELECT 2 FROM DUAL;
If your cursor is on the first select, and you run statement, it works just fine. But if your cursor is on the second statement, the “code” actually being executed is the ; in the second row(it gets briefly marked and throws error Unknown Command).
If you remove the extra ; at the end of the first line, it works just fine.
I haven't seen this bug reported yet, and its not that big a deal, but it is a minor annoyance, especially if you dont know why its happening.