Feature/improve coverage source query by jgebal · Pull Request #981 · utPLSQL/utPLSQL

Resolves #970

@rafael-trevisan - Will you be able to apply the changed package body on your DB, that was causing problems and confirm that it is working as expected?

This PR includes a different solution to the one your DBA has applied but it should also work fine.
The changed query syntax also applies some readability improvements to the code.

Hi @jgebal, I confirm the change that @fabiopan has done is already in our DB and works beautifully. We've been generating the Coverage Report since the last couple days without any problem and its line number is accurate.

We did some improvement in the original workaround, so the version @fabiopan has posted is the lastest one.

The code is much more readable due to the code templates. And the query does not need subqueries anymore. That’s good. However, the optimizer has still the freedom to completely rewrite the statement. If this results in a bad plan (for all/dba_source access) then further named subqueries to isolate all/dba_source access with a no_merge or materialize hint might help. I’d go with this change “as is” now.