Curious what real-world files people are dealing with. If you had a "SQL for files" tool sitting in your editor, what would be the first ugly thing you'd try to query?
A 20 GB Parquet dump? A folder of nested JSON logs? A CSV with 400 columns and no header? Something worse?
Reply with the file (or describe it) I'll test File SQL against the weirdest ones and post results here. Free stress test
Every analyst has stared at a folder of Parquet or CSV files and thought: "I just want to SQL this." File SQL does exactly that — inside VS Code.
Drop in a file path, an S3 URI, or a whole folder. Each subfolder becomes a table. Query it with DuckDB. Done.
Why it stands out: Local files and S3 — one extension, one workflow, Right-click any file in Explorer → instant SQL table, Multi-tab query editor with autocomplete, Runs entirely on your machine
