Re: Frustrated SQL Plus user

"Matt B." wrote:
>
> "dizzy" <dizzy73_at_connix.com> wrote in message
> news:393A6B94.200DCF99_at_connix.com...
> > Im running personal Oracle 8.05 which apparently dosnt have sql worksheet
> which Im accustomed to. I don't like the fact that the past commands are not
> saved in a buffer no use of the left arrow to modify a previous statement
>
> I've never seen SQL*Plus do that (unless I've been missing something for 7
> years...?).

heh... thats probably because sql+ dosnt behave (like sql worksheet)
>
> >I think its insane to have to retype a command I previously typed while in a
> session.
>
> 'ed' will put you into the default text editor (Notepad most likely on a
> Windows machine and vi on a UNIX machine) to modify your last statement.

[Quoted] [Quoted] well, if I envoke the editor it seems to interfer with the sql+ window both dont like to be open at the same time. To me thats an unacceptable "workaround" heck it dosnt work on my system!
>
> You can save your previous statements as you do along by typing "save
> <filename>" or "save <filename> repl" (if overwriting an existing file. File
> will have a .sql appended onto it if you specify no extention.

well, I dont want to "save" my querries

1 Im just practicing... getting a feel for where things are 2 If Im doing serious querries the statements are all "on the fly" so to speak. I think its insane to have to save the querries (say 6 querries in history)just because the program cant save the session statements in a buffer!

if I wanted to save a querry I would save it the call by _at_\filename

>
> Call it back up with "get <filename>" (and again the .sql will be assumed if
> you don't specify it) into the buffer or "start <filename>" to call it into the
> buffer and subsequently run it.

well the buffer (is really streching the term) can only handle *one* statement!
yep and I can save statements and call them by _at_path\to\filename thats not what I want
In dos I have doskey in the autoexec.bat so I dont have to retype in Linux/unix my session commands are all in a *real* buffer sql worksheet has a command history

for sql+ to be enamored as is is..... I just dont get it.... It sucks!

this is my whole gripe!

>
> >"the semi colon is optional..." Well its either a semi colon or type run
> after issuing the statement!
>
> SQL> select 'x' from dual;
>
> OR
>
> SQL> select 'x' from dual
> 2 ;
>
> OR
>
> SQL> select 'x' from dual
> 2
> SQL> /
>
> ...will all work.

so we have 2 semi colons and a /
 run will also *recall* the previous statement as well Thats another one of my gripes I want a keyboard shortcut eg ctrl+somecharacter
I dont want to have to terminate a simple querry however I could live without those, but the whole "command buffer" is killing me

[Quoted] [Quoted] I really dont see why sql+ is in such high regard. Imo its a horrible tool

thanks

rob Received on Sun Jun 04 2000 - 00:00:00 CEST