Comments on: Navigation in Large PL/SQL Code https://www.salvis.com/blog/2020/10/10/navigation-in-large-pl-sql-code/ Database-centric development Sun, 12 Nov 2023 12:52:54 +0000 hourly 1 https://wordpress.org/?v=7.0 By: Philipp Salvisberg https://www.salvis.com/blog/2020/10/10/navigation-in-large-pl-sql-code/#comment-41997 Thu, 28 Jan 2021 18:09:22 +0000 https://www.salvis.com/blog/?p=10753#comment-41997 In reply to Pavel Vetesnik.

Thank you Pavel for the heads-up.

I made some tests and the parameter parseThreshold still works in SQL Developer 20.4.0. However, the events to read this parameter and applying the changed value the background parser is different. From a user-perspective it is a bit delayed. So, to reproduce the example with a too low value for parseThreshold you have to open a new worksheet after changing the parameter. Then the code outline will use the new settings.

The new popup window that indicates a too low value for parseThreshold is in fact an improvement.

]]> By: Pavel Vetesnik https://www.salvis.com/blog/2020/10/10/navigation-in-large-pl-sql-code/#comment-41996 Thu, 28 Jan 2021 17:02:03 +0000 https://www.salvis.com/blog/?p=10753#comment-41996 Thank you very much for this explanation.
I believe that something has changed between Developer 20.2. and 20.4. I didn’t see this problem in older versions, but after upgrading to 20.4. I got messages “Exceeeded default parse threshold.” (and the “CTRL underline” ability was lost – but the shortcut SHIFT+F4 worked).
I think I don’t have huge packages.
Increasing number of tresholds fixed the problem.

]]>