Humm, Looks like someone could use a review of the SQL*Plus command
reference:
SET SQLBL[ANKLINES] {ON | OFF}
This ends that problem.
Dick Goulet
Senior Oracle DBA
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Nuno Souto
Sent: Wednesday, December 29, 2010 3:38 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: Re: SQLPLUS training, why?
Kellyn Pedersen wrote,on my timestamp of 29/12/2010 2:10 AM:
Yes and then some... considering the technical level of many who will
be
attending, do you really want them playing around with regular
expressions?? I
was referring to ones who might use MSWord, Text editors and Excel
spreadsheets
to create SQL that could be easily generated inside SQL Plus. When I
picture
these folks, I would never consider just throwing them into the deep
end of the
pool with RE's and say, "Swim!" :)
If there is one thing that drives me nuts with that mob - and the
Toad/sqldeveloper one as well - it's the blank lines in between a single
SQL
statement: guaranteed to screw up a long script when run from
SQL*Plus...
I now run a vim macro through every script originating from that stable!
Yes and then some... considering the
technical level of many who will be attending, do you really
want them playing around with regular expressions?? I was
referring to ones who might use MSWord, Text editors and Excel
spreadsheets to create SQL that could be easily generated
inside SQL Plus. When I picture these folks, I would never
consider just throwing them into the deep end of the pool with
RE's and say, "Swim!" :)
Kellyn Pedersen
Sr. Database Administrator
http://www.linkedin.com/in/kellynpedersen
www.dbakevlar.com
But I think that Kellyn's point was that improper use of regular
expressions is the source of many clbuttic errors ...
On 12/28/2010 02:24 PM,
TESTAJ3@xxxxxxxxxxxxxx