is it possible to run something like "history XX run" with sqlcl

user499562

Hi,

I'm playing around with sqlcl and I was wondering if it is possible to re-run a command (without copy/pasting it in the console) that is in the history buffer.

f.ex. running the history command returns a lot of entries, and if I would like to rerun the following commands f.ex:

48  select * from employees;

49  select * from regions;

In sqlplus you can do something like:

history 48 run

or

history 49 run

and the commands are run again.

>help history

doesn't seem to have any similar commands

history [<index> | FULL | USAGE | SCRIPT | TIME | CLEAR (SESSION)?]

Is it possible to do the same in sqlpl or something similar?

Or would you have to copy/paste it, or scroll history with the up/down keys (+ enter)?

Thanks a lot!

Didier

Glen Conway

Note that history <number> places the statement in the buffer so that

history 48run

or

history 48/

will do what you want.  And since the syntax you mention works in sqlplus, maybe the SQL Developer/SQLcl team will add support for that in a future release in order to keep closer compatibility with sqlplus.

Cheers

Glen Conway

Note that history <number> places the statement in the buffer so that

history 48run

or

history 48/

will do what you want.  And since the syntax you mention works in sqlplus, maybe the SQL Developer/SQLcl team will add support for that in a future release in order to keep closer compatibility with sqlplus.

Cheers

thatJeffSmith-Oracle

we built the history command, so the SQL*Plus can follow our lead if they'd like

Glen Conway

Touché! 

The sqlplus history command doc is not available using HELP in 12.2 sqlplus client (at least via Oracle instant client), but is in the online docs:

https://docs.oracle.com/en/database/oracle/oracle-database/12.2/sqpug/HISTORY.html#GUID-CCF9B047-3122-4644-BA06-5FA4B581…

And here is supporting evidence of your assertion that SQLcl provided the HISTORY command first:

https://www.realdbamagic.com/sqlplus-history-command-12cr2/

Comparing the documentation, it is clear that these are two distinctly different beasts and the two teams have distinctly different thought processes.  Congratulations to the SQL Dev team for "thinking different".

user499562

Thx ... almost to easy to have missed it ;-).