Skip to Main Content

SQLcl

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Windows Terminal: SQLCL 21.3 using statusbar causing issue for scroll

Kevin ZhangDec 1 2021

Hi All:
I am using Microsoft Terminal application to launch SQLCL.
My computer: Windows 10 64-bit (20H2)
Windows Terminal: 1.11.2921.0
SQLCL: 1.11.2921.0
if I enable statusbar by adding below lines in my login.sql, I will run into a weird issue related to scrolling. See below for further details:
set statusbar add editmode
set statusbar add txn
set statusbar add timing
set statusbar add cwd

The issue is: if I run a simple SELECT with generate many lines of output (for example few hundreds lines), in Windows Terminal, I can't use my mouse wheel to scroll up to see my output.
if I remove all above setting about statusbar from my login.sql, I don't have issue: I can use my mouse wheel to scroll up to see my output.
Also, if I set statusbar in my login.sql and use Window's Command Prompt application to launch SQLCL, I don't have any issue to scroll up to view the output.
Per my study, SQLCL's statusbar doesn't work well with Windows Terminal. I think Oracle SQLCL team can say "this is Windows terminal issue". But, given Windows Terminal is getting more popular (it is my go-to tool now) and I hope Oracle SQLCL team can fix this issue in future release.
Thank you!
Kevin (fan of SQLCL & Microsoft Terminal)

Comments

Ashish Dave-Oracle
either there is Synchronization issue or
element which was there at time of recording is not there while playback ..could be defect
or name or id of elemet changed
647280
You should create a better custom dynamic variable to identify this element. Referencing a element by Index is not recommended or reliable. A recorded Index of 41 for the element inside form QUERYTEXTCOMPONENTS indicates that there are a lot of elements inside that recorded form, and that there is probably some dynamic nature to the page.

You should change the match to be i.e. formelement[INPUT](name="something" | id = "something")
1 - 2

Post Details

Added on Dec 1 2021
1 comment
584 views