Debugging PL/SQL
It is important with any programming language either to be able to follow the code line by line or to be able to stop the code at certain points to check the contents of variables to ensure that the program is functioning as intended. Being able to visually see the code executing is an important ability when debugging or trying to find errors in the code. For example, if the expected result is not returned or the program never ends (a possible run-away loop), it would be nice to be able to step through the code, line by line, and check all the contents of all the variables.
Figure 3.22 uses Quest SQL Navigator to visualize the variables, including the returned values from the SQL statement with each iteration of the loop. Notice ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access