Re: Procedure Builder variables

From: Eric Givler <egivler_at_flash.net>
Date: Thu, 11 Jan 2001 02:27:58 GMT
Message-ID: <OS876.1674$J%.198731_at_news.flash.net>


    I'm not a procedure builder guru, but when I use it to test, I create a "stub" program to test the one that I'm going to debug. In that program, I create the variables and pass them as parameters to the routine in question. I compile this stub and set a break point as the first line in it. I then type <procname>; in the pl/sql window and it fires the program off (the stub) and I can step into the code to debug the other procedure. When it returns, I can see the output of these variables is returned to the stub and I verify the contents are what I expected. I continue this with several sets of variables. If it all looks good, then I build a script that does the same thing using seed values from a table, and output columns are populated after the procedure call. I run this in Plus.

    I hope that helps. It may not be the best way, but heck, I haven't been to training since '93, so I go with what makes sense to me.

"Sabens" <sabensgbcm_at_mindspring.com> wrote in message news:93ip3m$omt$1_at_slb3.atl.mindspring.net...
> Is there a way to create a return variable when trying to run a procedure
 in
> debug? I have two IN / OUT variables ( varchar2(1) and a varchar2(255)) in
> my procedure and I want to walk the code in debug. I have used the .CREATE
> function to establish variables (not sure if this is right ) but the
> debugger errors out and says I have to initialize them. Oracle docs
 doesn't
> cover this. Any help would be appreciated.
Received on Thu Jan 11 2001 - 03:27:58 CET

Original text of this message