data explorer: duckdb sql backend for convert to code

[isabelizimm]

Since we store the active where and sort clauses, we can probably just reuse them to show to users. Since these are what is filtering/sorting the data explorer, I assume they won't be stale. I haven't dug around too much to see if there are any other drawbacks to reusing these, but it does make this feature quite simple!

Release Notes

New Features

• data explorer: create SQL convert-to-code backend for duckDB sessions #8986 Add Convert to Code that generates SQL for headless Data Explorer sessions.

Bug Fixes

• N/A

QA Notes

• Open up "flights.parquet" file in positron-qa-examples
• Do some filters, sorts, etc. DuckDB displays the number of rows only if it's less than 9999, so if you want to do a quick sanity check that it's equivalent to number of rows in the data explorer, make sure you narrow it down accordingly!
• Convert to Code button -> copy to clipboard
• In Python, pip install duckdb
• Run ⏬

import duckdb

conn = duckdb.connect()
conn.execute("CREATE TABLE flights AS SELECT * FROM 'data-files/flights/flights.parquet'")

conn.execute(""" 
ADD COPIED SQL HERE
""").df()

[github-actions]

E2E Tests 🚀
This PR will run tests tagged with: @:critical

^{readme  valid tags}

[Copilot]

Pull Request Overview

This PR implements DuckDB SQL backend support for the "convert to code" feature in the data explorer. The change enables users to convert their current data explorer view (including filters and sorts) into executable SQL code that can be copied and run in Python with DuckDB.

Key changes:

• Added support for converting data explorer state to SQL code
• Implemented code syntax suggestion functionality
• Updated backend state to indicate convert-to-code support

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
extensions/positron-duckdb/src/extension.ts	Implements convert-to-code functionality with SQL generation and adds RPC handler support
extensions/positron-duckdb/src/test/extension.test.ts	Updates test expectations to reflect convert-to-code support status

[isabelizimm]

by default, it doesn't seem like there is syntax highlighting available unless you have an extension with a sql lsp

[wesm]

Do you want to try to add some extension tests? I can also add some in a follow up PR. The code changes look good to me though

[isabelizimm]

I can add some extension tests! It looks like there are context files for positron-duckdb, so I'll try my hand at using Claude Code for building them out. 🤞