Yes, I have the same experience with Jeff. I brought to his attention a
bug with tnsping and it was fixed in the next release. I would suggest
to have SQL init file for SQLcl named something like $HOME/.sqlcl.sql
or set up by an environment variable.
Also, it would be about time to switch from "afiedt.buf" ("AFI" comes from "A Friendly Interface", a predecessor of SQL*Plus) to ufiedt.buf. UFI or "User Friendly Interface" came after AFI. SQLcl would be the right time to catch up with the times:
This is humour for those among us who can remember attempting to set oraterm to work with 4800 bps modems, probably Jonathan, Mark, Jared and few others.
On 6/21/19 5:24 PM, Jared Still wrote:
I have found Jeff to be very responsive to such issues.--
Would you like '@somescript.sql' to work while embedded in SQL?
I have used that many times, and still do occasionally.
Once brought to Jeff's attention, it wasn't long before sqlcl could do that as well.
Certifiable Oracle DBA and Part Time Perl Evangelist
Principal Consultant at Pythian
Pythian Blog http://www.pythian.com/blog/author/still/
On Sat, Jun 15, 2019 at 10:04 AM Mladen Gogala <gogala.mladen@xxxxxxxxx <mailto:gogala.mladen@xxxxxxxxx>> wrote:
I am using a brand new Oracle 19c test VM and unfortunately, I am not
the only one. Since both SQLcl and sqlplus come with the
opted for sql and have put "set sqlformat ansiconsole" among other
things in $ORACLE_HOME/sqlplus/admin/glogin.sql because both sql and
sqlplus are reading that file. However, my colleagues are getting an
error when they attempt usng sqlplus, so I have removed the offending
directive from glogin.sql. Since those tools are diverging more and
more, would it be possible to separate the initialization SQL
This question is primarily for Jeff Smith, the product manager.
-- Mladen Gogala
Tel: (347) 321-1217