Converse agora com nosso suporte
Chat com o suporte

Toad for Oracle 2024 R2 Common Documents - Getting Started Guide

Welcome to Toad Toad Resources Required Privileges Create and Manage Database Connections Editor Basics Schema Browser Basics Data Grid Basics Work with Data Work with Database Objects Work with Code
Write Statements and Scripts Work with the Query Builder Execute Statements and Scripts Save Statements (SQL Recall) Work with PL/SQL Objects Debug Analyze Code Optimize SQL
Customize your Toad Environment Use Other Quest Software Products with Toad

Stop the Debugger

If you are debugging a long procedure, you can stop the debugger while it is working.

To stop the Debugger while it is debugging

  1. Click .

    The status panel will reset from Running to Idle.

  2. When you have finished debugging your PL/SQL code, discard the debug symbol table: compile it again by pressing F9.

 

Prepare PL/SQL Code for Production

When you have finished debugging your PL/SQL code, the debug symbol tables are left in the code. This makes your code larger and can slow performance. To eliminate this issue, compile the code and its dependencies and references one last time without debug information.

To compile without debug information

  1. On the main toolbar, turn the debug toggle button to the off position (not depressed).
  2. Compile the code. This recompiles without the debug symbol tables.

 

View Debug Results

Toad sends your PL/SQL debugger output results to the PL/SQL Results window. This window is located on a tab in the output area of the Editor.

When the PL/SQL execution terminates, the PL/SQL Results window displays the input and output of the code, in a format similar to that shown in the Set Parameters window (parameter name, data type, input, and output). If there is a cursor result, you can view the data stored in each REF CURSOR that is returned via out parameters or as a function result.

From this window, you can create new unit tests (Code Tester for Oracle and utPLSQL), run Code Tester for Oracle unit tests, and also open Code Tester for Oracle. Create and Run Unit Tests From Execution Results

The PL/SQL Results window has the following limitations:

  • Works only with strongly-typed REF CURSORs.
  • Works only when the REF CURSOR type is declared in a package belonging to the currently logged-in user.

To view cursor data

  • Before you execute the PL/SQL, select Fetch cursor data in the Set Parameters window. Set Parameters
  • After you execute the PL/SQL, double-click (CURSOR) in the PL/SQL Results window.

To access the PL/SQL Results tab

If you cannot see the PL/SQL Results window at the bottom of the Editor, try one the following:

  • In the Editor toolbar, select PL/SQL Results from the Desktop drop-down menu.
  • Right-click in the Editor window and then select Desktop | PL/SQL Results.
  • If PL/SQL Results is already active but still not visible, then you may need to resize or reposition the docked windows to make it visible.

 

Use DBMS Output

Toad provides an intuitive and efficient way to write, run, and test your SQL and PL/SQL code. Toad supports efficient code management for a single developer or a whole team of developers.

 

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação