If I am working in a PL/SQL package and re-compile from SQL*Plus, PL/SQL Dev is aware of the outside change and asks me, via dialog, if I would like to reload the package. When clicking "Yes," the code appears to reload, but what is displayed is actually the same code that existed prior to the re-compile (i.e. the code doesn't actually reload).

If there are compile errors, PL/SQL Developer is aware of the errors and displays a nice list of errors and their associated package line numbers in the area below the code editor area. If I click on one of these errors, however, it takes me to the right line # in the old version of the code.

The only way around this is to close the current view/edit window for the package from the window list, locate the package within its schema, and reload the package. Only then is the new code displayed. With over 100 schemas, and some of those schemas containing as many as 2,000 packages, and working with 10-15 packages at a time, this is an unwieldy solution to the problem.

From the Support Info window in PL/SQL Developer:
Using Oracle 11g

We'll check it out.

Thanks!

We cannot reproduce this yet. It seems to work just fine.

Strange... Every developer in my shop has this problem. What would you need from us to further investigate the problem?

Thanks,
Brad

To obtain some more diagnostic information, can you modify the shortcut and add the DebugSQL parameter? For example:

"C:\Program Files\PLSQL Developer\plsqldev.exe" DebugSQL

Reproduce the problem and send me the debug.txt file that is generated in the PL/SQL Developer directory or in the %APPDATA%\PLSQL Developer directory (e.g. C:\Users\<User>\AppData\Roaming\PLSQL Developer).

I catched this bug too. I editing code on Program Window and when I recompile package body on sqlplus with old-code .pkb PLSQLDeveloper prompt me reload opened code in editor from DB. When I agree do it then code in editor stay without any changes.

Marco,

Any suggestions on how to quickly get to a package body in a large schema with DebugSQL enabled? I found that I could get to it from a "Find Database Objects" search, but the search has been running for nearly an hour now with only 2-3% progress with DebugSQL enabled (very large schema).

Similarly, opening the package body from the "Objects" window pane doesn't work, either; right-clicking on the object causes the application's UI to lock up while writing to the debug file. I assume there must be some sort of timeout that lapses because of this, and the context menu never shows (from there, I would normally click on one of the "View/Edit Spec & Body" options) to open the package body.

Thanks,
Brad

Please send me the debug.txt file that is created when you right-click on the package body.

Marco,

I emailed a zipped-up version of my Debug.txt to the support e-mail address Wednesday. Did you receive it?

Thanks,
Brad