Claus Pedersen
Member³
I have some enhancement requests to the profiler:
1) Save the source line text in a extra column in the table "plsql_profiler_data". Now, only the line number of the source code is saved. This means, that if you add or delete lines in the source code during a refactoring or enhancement process, the text shown for code lines for old profiler runs are not the correct ones, because the saved line numbers are not corresponding to the line number in the newly changed source. If this is omitted intentionally because of speed or space issues, this could maybe be an optional feature when turning the profiler on?
2) Make it possible to print the data of the table "plsql_profiler_units", shown in the Unit dropdown, together with the rest of the profiler lines (elapsed time in each unit). This could be optional via a checkbox? Maybe also print the database user to help identify the run (or include in the run header)
1) Save the source line text in a extra column in the table "plsql_profiler_data". Now, only the line number of the source code is saved. This means, that if you add or delete lines in the source code during a refactoring or enhancement process, the text shown for code lines for old profiler runs are not the correct ones, because the saved line numbers are not corresponding to the line number in the newly changed source. If this is omitted intentionally because of speed or space issues, this could maybe be an optional feature when turning the profiler on?
2) Make it possible to print the data of the table "plsql_profiler_units", shown in the Unit dropdown, together with the rest of the profiler lines (elapsed time in each unit). This could be optional via a checkbox? Maybe also print the database user to help identify the run (or include in the run header)
