Feature Description
When exporting results from a SQL Notebook cell to CSV, JSON, or Excel, the success toast displays the saved file path but provides no action to open the file. The Query Profiler already solves this with an Open File button on its export-success toast. SQL Notebooks should match.
Current Behavior
After running an export from a SQL Notebook result grid, the toast shows:
Saved results to /Users/<user>/Untitled-1_resultset_1.json
Source: SQL Server (mssql)
No action buttons are available on the notification. The user must navigate to the path manually in their OS file browser to open the file.
Expected Behavior
The export-success toast should include an Open File action (matching the Query Profiler experience) that opens the exported file in VS Code, and ideally also a Reveal in Finder / Show in Explorer action to open the containing folder.
Problem and Motivation
SQL Notebooks are explicitly positioned for iterative, interactive analysis. An export almost always leads to a next step (open, inspect, attach, share). Hiding that next step behind manual OS navigation breaks the flow inside VS Code. The Query Profiler already demonstrates the correct pattern in the same extension.
Related Area
If you selected "Other", please describe the area
SQL Notebooks
Confirmation
Feature Description
When exporting results from a SQL Notebook cell to CSV, JSON, or Excel, the success toast displays the saved file path but provides no action to open the file. The Query Profiler already solves this with an
Open Filebutton on its export-success toast. SQL Notebooks should match.Current Behavior
After running an export from a SQL Notebook result grid, the toast shows:
No action buttons are available on the notification. The user must navigate to the path manually in their OS file browser to open the file.
Expected Behavior
The export-success toast should include an
Open Fileaction (matching the Query Profiler experience) that opens the exported file in VS Code, and ideally also aReveal in Finder/Show in Exploreraction to open the containing folder.Problem and Motivation
SQL Notebooks are explicitly positioned for iterative, interactive analysis. An export almost always leads to a next step (open, inspect, attach, share). Hiding that next step behind manual OS navigation breaks the flow inside VS Code. The Query Profiler already demonstrates the correct pattern in the same extension.
Related Area
If you selected "Other", please describe the area
SQL Notebooks
Confirmation