Re: Good editing environment....?

Use Textpad 3.0 - it is the best Windows editor available and it is cheap ($30). Get it from www.textpad.com. A lot of sound editing functionality. Next, set up your environment so you don't have to cut and past or use @c:\blah\blah\blah.sql a lot.

1. Go into the registy
2. Search for SQLPATH under Oracle's software entry
3. Append a ;path where you keep your working files. Ending result will look like c:\orant\dbs;c:\work\sql
4. open SQLPLUS and compile a file in your working directory to test it.

Mark Madsen
mark.madsen_at_tswi.com

Tomm Carr wrote:

> Kenn Herman wrote:
> >
> > The way I have been editting procedures is to have a scratch window
 to
> > write my procedure in including the "create or replace" and the
> > trailing "/". Once I am ready, I paste it into the sqlplus command
 line.
> > well once there I can edit it with the editor of my choice, but as
 soon as
> > I make any other SQL args then the buffer is lost. I have to then
 "select
> > text from user_source where name = 'PROCEDURE_NAME';" to retrieve it
 and
> > the paste it back to my scratch window.
> >
> > I am _sure_ there has to be a better way then this but have seen no
> > reference to it.
>
> A good editing environment, hmmm... Well, on Windows I use Wordpad.
> The
> procedure is something like this:
>
> 1) Open (or create) the source file in Wordpad.
> 2) Save the file. Don't close or exit, just save.
> 3) Alt-TAB to SQL-Plus.
> 4) Enter "@filename" to execute the source
> 5) Observe errors or output.
> 6) Slap your forehead soundly for making such a stupid error!
> 7) Alt-TAB to Wordpad and fix the mistake(s).
> 8) Goto step 2.
>
> Not fancy, but it works for me.
>
> P.S I even have a similar method when I am on the VAX. I just have to
>
> open two terminal sessions, one for EDT and one for SQL*Plus.
>
> --
> Tomm Carr
> --
> "Can you describe your assailant?"
> "No problem, Officer. That's exactly what I was doing when he hit
> me!"
Received on Tue Jul 22 1997 - 00:00:00 CDT