Re: Another SQLcl quirk

+1 on praise for sqlcl and Jeff.

I see 19.2 is not available on TechNet yet. Hoping it fixes the bug whereby sqlcl 19.1 forces use of the ORACLE_HOME JDK if $ORACLE_HOME is set on a DB server and it's 11gR2. Anyone else experience that?

Thanks.

--
Jack C. Applewhite - Database Administrator
Austin I.S.D. - MIS Department
512.414.9250 (wk)

I cannot help but notice that there is no problem between us that cannot be solved by your departure.  -- Mark Twain
________________________________
From: oracle-l-bounce_at_freelists.org <oracle-l-bounce_at_freelists.org> on behalf of Mladen Gogala <gogala.mladen_at_gmail.com>
Sent: Friday, July 12, 2019 10:07:12 AM
To: Jeff Smith <jeff.d.smith_at_oracle.com>; oracle-l_at_freelists.org <oracle-l_at_freelists.org>
Subject: Re: Another SQLcl quirk


Thanks Jeff!

You are great, not to mention the product.

Regards

On 7/12/19 10:47 AM, Jeff Smith wrote:

Appears to be



SQL> show version

Oracle SQLDeveloper Command-Line (SQLcl) version: 19.2.0.0

SQL> set history fails

SQL> show history

HISTORY

        enabled

        blacklist: show,history,connect,set

        Show failed statements:(20 statements)

SQL> select 1 form dual;



Error starting at line : 1 in command -

select 1 form dual

Error at Command Line : 1 Column : 15

Error report -

SQL Error: ORA-00923: FROM keyword not found where expected

00923. 00000 -  "FROM keyword not found where expected"



*Cause:





*Action:



Elapsed: 00:00:00.387

SQL> history

History:

  1  lb help genobjecet

  2  lb help genobject

  3  cd c:\SQLDev\sqlcl\192-final\sqlcl\lb\rest-demo\v1

  4  desc locations

  5  info locations

  6  info+ locations

  7  select * employees;

  …

49  select * from regions;

50  select 1 form dual;

SQL>



From: Mladen Gogala <gogala.mladen_at_gmail.com><mailto:gogala.mladen_at_gmail.com>
Sent: Friday, July 12, 2019 10:40 AM
To: oracle-l_at_freelists.org<mailto:oracle-l_at_freelists.org>
Subject: Another SQLcl quirk



I can't get it to show failed lines:

SQL> set history limit 50 fails
SQL> show history
HISTORY
        enabled
        blacklist: show,history,connect,set
        Do not show failed statements
        Max Size: 50
SQL> show version
Oracle SQLDeveloper Command-Line (SQLcl) version: 19.1.0.0
SQL>

This looks like a bug. Will it be fixed in the next release, which is due in a couple of days?

Confidentiality Notice: This email message, including all attachments, is for the sole use of the intended recipient(s) and may contain confidential student and/or employee information. Unauthorized use of disclosure is prohibited under the federal Family Educational Rights & Privacy Act (20 U.S.C. §1232g, 34 CFR Part 99, 19 TAC 247.2, Gov’t Code 552.023, Educ. Code 21.355, 29 CFR 1630.14(b)(c)). If you are not the intended recipient, you may not use, disclose, copy or disseminate this information. Please call the sender immediately or reply by email and destroy all copies of the original message, including attachments.

--
http://www.freelists.org/webpage/oracle-l