In Java/Classic Oracle SQL Developer 24.3.1, I have options to enable compiler warnings in the settings:
This will give me hints about things I should fix in the code, like unreachable code, IN/OUT copy hints, and so on:
In VS Code (25.2.2) there are no such settings. However I did get a hand from Doug Gault (thank you!) to do the same using a startup script:
The file contains:
--login.sql
ALTER SESSION SET PLSQL_WARNINGS = 'ENABLE:ALL';
ALTER SESSION SET PLSQL_OPTIMIZE_LEVEL = 2;
This is what I see in VS code:
It seems to suggest these are errors, although the package IS compiling, and if I query all invalid objects, it is not in the list.
So - can anyone confirm, this is all ok to use? I am guessing VSCode UI doesn't have the concept of warnings yet, with a little yellow exclamation point, but so long as I pay attention to PLW for warning vs PLS for error, it should be ok to use this way?
Thank you for the input!
Doug