René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Optimize availability check for \"Run utPLSQL test\" menu option","articleBody":"In the preferences you can configure if you want to check for the availability of the menu option \"Run utPLSQL test\". When set, the extension enables the menu option only when at least one test has been found. This may be slow for two reasons:\r\n\r\n1. because the annotation cache needs to be updated\r\nthis happens only, if you do not use a DDL trigger to track changes, in this case changes are detected delayed, when running a test or when checking for availability of tests\r\n\r\n2. large schemas\r\nthere is more data in the annotation cache and in the data dictionary, affecting the runtime performance of the queries, especially when no DDL trigger is in place, due to delayed annotation detection\r\n\r\nSince version 3.1.8 the following functions are available in `ut_runner`: \r\n\r\n- `has_suites`\r\n- `is_suite`\r\n- `is_test`\r\n\r\nThese functions are optimized for performance and are faster than the generic table function `get_suites_info`. Hence these functions should be used whenever possible by the SQL Developer extension.\r\n\r\nIn fact these functions are available since utPLSQL version 3.1.3, but since version 3.1.8 they are considered reliable (see also utplsql/utplsql#976). Hence the use of this functions should be limited to utPLSQL version 3.1.8 and higher.","author":{"url":"https://github.com/PhilippSalvisberg","@type":"Person","name":"PhilippSalvisberg"},"datePublished":"2019-07-16T04:45:12.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":12},"url":"https://github.com/76/utPLSQL-SQLDeveloper/issues/76"}