You cannot disable it. This change in behavior actually occurred in 4.2. The common code shared by SQLcl and SQL Developer was modified to conform to SET ECHO ON behavior in SQL*Plus. For example...
Of course, you might perform the additional work of removing those line numbers yourself in order save others from the trouble of doing it.
Gary and Jeff,
Thanks for the responses.
If I need to do additional work as you both suggest, it nullifies the use of set echo on for me (in the context I use it for).
I guess I can still copy paste the result set separately.
You could use the PROMPT command instead to show the SQL, it's still more work, but it's available.
1 person found this helpful
there's always a chance
Thanks for the encouraging words.
While I understand that showing the line number in the output brings "consistency" (?) with sqlplus and sqlcl, there is always a chance an ordinary Joe who could be using it for something and very pleased with that feature (however trivial it may be and if it breaks there is always a workaround), will be deprived of that.
I love the feature. In fact, you taught me how to get there in a previous thread. A big thank you for that. I also want utilize the custom formatting that comes with 17.3.1. So, now I can't make up my mind between 4.1.5 and 17.3.1.
I totally understand this probably even won't fit in as the last item in your list of concerns for the product.
Hope I managed to get you to read up to here.