[buzzia2001]

Changes

Export the result set as CSV, JSON, Markdown or SQL INSERT (#588)

• New "Export as..." submenu in the result set toolbar, both in the panel view and when the result set is moved into the editor area.
• Each format opens in a new untitled editor tab, the same way the csv:, json:, md: and sql: statement prefixes do. The prefixes and the menu now share the same formatting code (export.ts).
• If not all rows have been fetched yet, a quick pick asks whether to retrieve all of them first or export only the loaded rows.
• CSV output uses the column delimiter setting and the decimal separator setting added in feat: add configuration for CSV decimal separator and update CSV formatting logic #594 (merged from main), for both the menu and the prefixes.

Parameter values in the result set (#589)

• When a statement runs with parameter markers (? or named :NAME), the info button in the result set toolbar now lists the values that were used, below the filter/sort text. It also shows when no filter or sort is applied, and for CALL statements.
• Named markers are listed as :NAME, positional ones as Parameter marker N, matching the bind prompt. A name used more than once is listed once.
• "Copy SQL" now writes the values into the statement as literals (with quotes escaped), so the copied SQL runs as is. With a filter or sort applied, the copied statement includes both.

Column details on the column heading (#590)

• Hovering a column heading shows the column metadata, like ACS: Name, Type, Precision, Scale, Nullable and Label, plus Table and Auto increment when available.
• Nullable, Table and Auto increment are only sent by newer Mapepire servers. With older servers those rows are left out.
• This replaces the previous native tooltip, which showed only the type and the label.

How to test this PR

1. Run the test cases (npm test). New suites: export.test.ts and parameterInfo.test.ts.
2. Run select * from qiws.qcustcdt where state= :thestate, enter the values in the prompt, and hover the info icon in the result set toolbar. The two values should be listed.
3. Click "Copy SQL" and paste: the values should replace the markers. Add a search filter and sort a column, copy again, and check that the pasted statement runs.
4. Open "Export as..." and pick each format: each one should open in a new editor tab. Before all rows are fetched, check that you are asked to retrieve all rows or only the loaded ones.
5. Hover a column heading: the column details should be shown.
6. Move the result set into the editor area and repeat steps 2–6.

Checklist

• have tested my change
• have created one or more test cases
• updated relevant documentation
• Remove any/all console.logs I added
• have added myself to the contributors' list in CONTRIBUTING.md

Closes #588
Closes #589
Closes #590

[github-actions]

👋 A new build is available for this PR based on ad6e318.

• Download here.
• Read more about how to test

[SanjulaGanepola]

Can we have Export as ... instead of Copy as... and pop the content into an untitled file just like the prefixes?