Re: Finding a PL/SQL error
From: Russ Seligman <rseligma_at_oracle.com>
Date: 1995/07/03
Message-ID: <RSELIGMA.95Jul2224707_at_seinfeld.oracle.com>#1/1
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Received on Mon Jul 03 1995 - 00:00:00 CEST
Date: 1995/07/03
Message-ID: <RSELIGMA.95Jul2224707_at_seinfeld.oracle.com>#1/1
As a followup to several posts discussing how to locate PL/SQL compilation errors in the non-intuitive SQL*Plus environment, I will once again post about the virtues of Oracle Procedure Builder. Procedure Builder is a GUI, interactive PL/SQL editor, compiler, and debugger. It graphically displays all stored program units and database triggers, and allows you to drag-and-drop them onto the client for debugging, then back to the server for deployment. The PL/SQL debugger is the only one on the market that lets you set breakpoints, step through your code, and examine and change the values of local variables.
You will never type SHOW ERRORS again.
--Russ
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Russ Seligman "If there's nothing wrong with me, maybe Oracle Developer/2000 there's something wrong with the universe." Oracle Corporation --Beverly Crusher, ST:TNG rseligma_at_oracle.com
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Received on Mon Jul 03 1995 - 00:00:00 CEST