Dial: A Knowledge-Grounded Dialect-Specific NL2SQL System
Not on the map. Why?
Abstract (arXiv)
Enterprises commonly deploy heterogeneous database systems, each of which owns a distinct SQL dialect with different syntax rules, built-in functions, and execution constraints. However, most existing NL2SQL methods assume a single canonical dialect (e.g., SQLite) and struggle to produce queries that are both semantically correct and executable on target engines. Prompt-based approaches tightly couple intent reasoning with dialect syntax, rule-based translators often degrade native operators into generic constructs, and multi-dialect fine-tuning suffers from cross-dialect interference. In this paper, we present Dial, a knowledge-grounded framework for dialect-specific NL2SQL. Dial introduces: (1) a Dialect-Aware Logical Query Planning module that converts natural language into a dialect-aware logical query plan via operator-level intent decomposition and divergence-aware specification; (2) HINT-KB, a hierarchical intent-aware knowledge base that organizes dialect knowledge into i a Canonical Syntax Reference, ii a declarative function repository, and iii a procedural constraint repository; and (3) an execution-driven debugging and semantic verification loop that separates syntactic recovery from logic auditing to prevent semantic drift. We construct DS-NL2SQL, a benchmark covering six major database systems with 2,218 dialect-specific test cases. Experimental results show that Dial consistently improves translation accuracy by 10.25% and dialect feature coverage by 15.77% over state-of-the-art baselines.
Key facts. No citing papers in the map yet (data through 7 Oct 2026). Builds on 26 of its 53 references that are in the map. First posted on arXiv 8 Mar 2026.
Builds on
26 of 53 references.
References · 26
- 2023Reflexion: Language Agents with Verbal Reinforcement Learningcited by 4,064
- 2023Large Language Models Cannot Self-Correct Reasoning Yetcited by 965
- 2017Seq2SQL: Generating Structured Queries from Natural Language using Reinforcement Learningcited by 679
- 2023Can LLM Already Serve as A Database Interface? A BIg Bench for Large-Scale Database Grounded Text-to-SQLscited by 667
- 2023DIN-SQL: Decomposed In-Context Learning of Text-to-SQL with Self-Correctioncited by 465
- 2023Text-to-SQL Empowered by Large Language Models: A Benchmark Evaluationcited by 378
- 2018Characterizing and Avoiding Negative Transfercited by 226
- 2024Spider 2.0: Evaluating Language Models on Real-World Enterprise Text-to-SQL Workflowscited by 223
- 2024CodeS: Towards Building Open-source Language Models for Text-to-SQLcited by 183
- 2019CoSQL: A Conversational Text-to-SQL Challenge Towards Cross-Domain Natural Language Interfaces to Databasescited by 180
- 2023MAC-SQL: A Multi-Agent Collaborative Framework for Text-to-SQLcited by 158
- 2019SParC: Cross-Domain Semantic Parsing in Contextcited by 141
14 more
- 2025OmniSQL: Synthesizing High-quality Text-to-SQL Data at Scalecited by 90
- 2024The Dawn of Natural Language to SQL: Are We Fully Ready?cited by 78
- 2024DTS-SQL: Decomposed Text-to-SQL with Small Large Language Modelscited by 45
- 2023Evaluating Cross-Domain Text-to-SQL Models and Benchmarkscited by 32
- 2025A Survey of Data Agents: Emerging Paradigm or Overstated Hype?cited by 30
- 2025DeepEye-SQL: A Software-Engineering-Inspired Text-to-SQL Frameworkcited by 26
- 2025Agentar-Scale-SQL: Advancing Text-to-SQL through Orchestrated Test-Time Scalingcited by 20
- 2024Archer: A Human-Labeled Text-to-SQL Dataset with Arithmetic, Commonsense and Hypothetical Reasoningcited by 13
- 2025ExeSQL: Self-Taught Text-to-SQL Models with Execution-Driven Bootstrapping for SQL Dialectscited by 11
- 2026Can LLMs Clean Up Your Mess? A Survey of Application-Ready Data Preparation with LLMscited by 9
- 2025DBAIOps: A Reasoning LLM-Enhanced Database Operation and Maintenance System using Knowledge Graphscited by 7
- 2025PARROT: A Benchmark for Evaluating LLMs in Cross-System SQL Translationcited by 5
- 2021Data Management in Microservices: State of the Practice, Challenges, and Research Directionscited by 3
- 2025An Empirical Study on Database Usage in Microservicescited by 1
Built on by
Not cited yet.