Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run Cell in INB document does not run with same code as CTRL+R #203

Closed
m-tyler opened this issue Feb 22, 2024 · 0 comments · Fixed by #165
Closed

Run Cell in INB document does not run with same code as CTRL+R #203

m-tyler opened this issue Feb 22, 2024 · 0 comments · Fixed by #165

Comments

@m-tyler
Copy link

m-tyler commented Feb 22, 2024

Run Cell in INB document does not run with same code as CTRL+R

If you write SQL in a INB document and run it using CTRL+R the newer DB2 for IBM i JDBC service is used.

  1. However, if you use the Execute Cell button (see image below) an attempt is made but it does not run the same and uses the older method that uses the QSHELL DB2 tool (call QSYS/QZDFMDB2 PARM('-d' '-i' '-t')).

  2. Also, if a cell happens to have a leading semi colon nothing happens. You will be returned a SQL statement empty or blank error even though the process sees all the SQL statements and passes them to call QSYS/QZDFMDB2 PARM('-d' '-i' '-t').

  3. Statement prefixes are not allowed with the Execute Cell feature.

Steps to recreate above issues:

  1. open or create a new document of type .INB
  2. insert code of type SQL
  3. insert more than one statement
    3.a add more than one statement without table qualifications.
    3.b precede the first statement to run with a semi colon
    3.c prefix any SQL statement with CSV: or JSON:
  4. results will be different depending on the test in 3.a-b
    4.a image
    4.b image
    4.c image

Note: using CTRL+R you can only run one statement at a time and only one under the cursor.

A low pty issue for me

Thanks, Matt

@worksofliam worksofliam linked a pull request Feb 22, 2024 that will close this issue
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant