Example of the Problem

When the “Check availability of menu option” in the “Run utPLSQL test” tab of the preferences is checked, then the following statements are executed twice on a right-click of a schema/user node in the Database Navigator window:

BEGIN
   ? := ut.version;
END;

DECLARE
   l_return VARCHAR2(1) := '0';
BEGIN
   IF ut_runner.has_suites(?) THEN
      l_return := '1';
   END IF;
   ? := l_return;
END;

The reason is, that there are two menu options:

• Run utPLSQL test
• Code coverage...

Each menu item needs to be enabled or disabled. Therefore the SQL Developer framework calls update per menu item (action). This cannot be changed by this extension. However, the extension can control the executions of the SQL statements.

Enhancement Request

Provide a SQL result caching mechanism. Via a DIY-implementation or via some standard functionality like the JDBC client-side result cache.