text to sql
technique judged 95% likely a named technique or architecture
See how it has spread across media tiers
Mentions over time
Table view
| Week | Articles | Sources |
|---|---|---|
| 2024-W14 | 1 | 1 |
| 2025-W51 | 1 | 1 |
| 2026-W01 | 2 | 1 |
| 2026-W27 | 1 | 1 |
| 2026-W36 | 1 | 1 |
In their words
The standard Text-to-SQL recipe hands the model the schema (a big text blob, or a search index of table docs) and hopes it picks the right tables.
Text-to-SQL with LLMs in Production: Schema Linking, Query Validation, and Guardrails (2026) A practical, evaluation-first guide to shipping text-to-SQL with LLMs in production: schema linking as RAG, semantic layers, three-stage query validation, and defense-in-depth guardrails, with runnable code and 2026 benchmark numbers.
We used the same approach for d0, our text-to-SQL agent.
We open-sourced bash-tool , the Bash execution engine used by our text-to-SQL agent that we recently re-architected to reduce our token usage, improve the accuracy of the agent's responses, and improve the agent's overall performance.
We spent months building a sophisticated internal text-to-SQL agent, d0, with specialized tools, heavy prompt engineering, and careful context management.
Initially fine-tuned from Meta’s original Llama-2–7b model using a broad dataset covering general SQL queries, DuckDB-NSQL-7B underwent further refinement with DuckDB text-to-SQL pairs.