Parameterised Queries: Interactive SQL Query Parameters in SQL Console

[Pinchez25]

Chat2DB Edition

Chat2DB Community

User Problem

When running the same SQL query repeatedly with different values in the WHERE clause, I currently have to edit the SQL each time to change the value.

For example, changing:

WHERE id = 42;

to:

WHERE id = 43;

every time I want to query a different record becomes tedious, especially for longer or more complex queries.

Concrete Use Case

It would be useful to define a parameter directly in the SQL:

SELECT
  report_name,
  report_type
FROM fineract_default.stretchy_report
WHERE id = :id;

When the query is executed, Chat2DB could detect :id and prompt the user to provide its value:

id: [ 42 ]

The same query could then be executed again with a different value without modifying the SQL.

This could also support multiple parameters:

SELECT *
FROM some_table
WHERE client_id = :client_id
  AND status = :status;

with Chat2DB prompting for both values when the query is run.

Product Area

SQL editor

Proposed Outcome

Add support for interactive SQL query parameters in the SQL editor.

When a query contains parameters, Chat2DB should:

1. Detect the parameters in the query.
2. Prompt the user for their values when the query is executed.
3. Bind the supplied values to the query.
4. Execute the query without requiring the SQL itself to be modified.

Named parameters such as :id would be particularly useful, although support for other parameter syntaxes could also be considered depending on the database/driver.

Alternatives Considered

No response

Contribution

I can help test the change

Submission Checklist

• I searched existing issues and Discussions for duplicates.
• I selected the affected Chat2DB edition.

[openai0229]

Thanks for the detailed write-up — the use case is clear.

We mapped where this would land, and it's a real feature rather than a small fix: the console sends the statement text untouched, the backend splits/rewrites it and executes via PreparedStatement with nothing bound, and there is no existing variable or parameter mechanism on the execution path. It would need a way to carry parameter values in the execute request, a binding step at execution time, and a new prompt dialog in the console — plus care around result paging, which re-executes the original SQL text.

Would you be interested in contributing this yourself? We can share the insertion points we identified and review a PR. If not, no problem at all — we'll keep it on the list; knowing your interest just helps us plan.

[Pinchez25]

I am interested in contributing to the code myself. Just tell me how to get started