codefori / codefori/vscode-db2i

Add prompting for Named Parameters for SQL Scripts

Open
#572 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
76
Forks
54
Avg merge
17m
Merged PRs (30d)
1

Description

⚠️⚠️ **Prompting for Named Parameters for SQL Scripts** ⚠️⚠️

I am trying to switch from using dBeaver SQL to DB2 for IBM i. I have used Named Parameter in my support SQL scripts. Eclipse prompts the list of named parameters when running the SQL Statement. It is much nicer since the named parameter can be used in multiple places in the SQL Script but prompts only once for the Parameter with the same name. To used the Bind: looks like you would have to supply the same value multiple times with the same value. It makes named parameters somewhat useless in DB2 for IBM i.
Also. what order would the values for parameters need to listed, by order of appearance in the SQL script or order of sub phrases execution in the SQL Script?

1. right click on any job (in the SQL Job Manager) and select the option to enabing tracing
2. recreate the issue with tracing enabled
3. right click on the same job again and get the tracing data
4. copy and paste that data into your new issue

**Sample SQL Script**

Image

**Prompt Provided in Eclipse**

Image

**Environment**

- OS: Windows 11 Enterprise
- Version [25H2]
- Db2 for IBM i
- Version 2.0.2

**Additional context**

Add any other context about the problem here.

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the request from the SQL Job Manager using the sample SQL script, then enable tracing and retrieve the tracing data as described in the issue. Trace how SQL scripts are executed and how bind values are collected; done means unique named parameters are prompted once and the parameter-value ordering is defined and covered by a reproducible check.

Written by the indexing model from the issue text.

Assessment

Tech stack
sql, typescript
Domain
database, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.