When using the debugger, occasionally the mode doesn't pick up on the correct type declaration (we have a custom object for error handlers and return codes that we utilize)
Sample Declaration:
TYPE error_rec is RECORD (
qy_sqlcode NUMBER(10) DEFAULT NULL,
tx_sqlerrm VARCHAR2(2000) DEFAULT NULL,
tx_trace_message VARCHAR2(32000) DEFAULT NULL);
When going to debug, it renders as CUSTPRO.PCPM.ERROR_REC%null even though ERROR_REC is a type itself.
If I click on “View PL/SQL” and try to update the code like we would do in Legacy/Classic, the updated PL/SQL is not used for debugging and is “lost” essentially. I receive the following error when trying to engage the debugger:
In legacy/classic SQL Developer, when the debug screen would come up, we could update the code to instead of trying to return the opaque type we would print the responses out using DBMS_OUTPUT statements. It also recognised the type declaration correctly.
If I update the PL/SQL block in the window and click OK, it uses my modified block correctly and starts the debugger.
As a result I think I have found 2 bugs for the team.
- Incorrect formatting of Debug PL/SQL when utilizing custom types defined in packages
- Inability to update PL/SQL Block for debugging session when using debug mode.