Re: Yet another tool for Command_line_history for Linux DBA

> Doing so on a SQL*Plus command line is less so.  SQL statements
> are often more than one line, so it is necessary to up arrow to each
> line in succession, making sure it is the correct line, and then hit
> enter.  Do this for each line in the statement.
Agree. I use rlwrap abilities to edit command line only for
one-liners. For the others I use vim.

> It is simply to easy in SQL*Plus to save the buffer to a file via
> the 'save' command, or simply 'get afiedt.buf' and 'ed'.
What I like in rlwrap is it's ability for word completion. I.e. I
created sql.dict file with sql keywords and words like dba_role_privs,
etc. and run 'rlwrap -f sql.dict sqlplus'.
After that, I type 'dba_ro' and press <tab> to complete it to
dba_role_privs (the same way as in my vim editor).

-- 
Egor
http://www.oracledba.ru/orasrp/
Free Oracle Session Resource Profiler
--
http://www.freelists.org/webpage/oracle-l

Other related posts: