EGREFINE: An Execution-Grounded Optimization Framework for Text-to-SQL Schema Refinement

arXiv cs.CL / 5/4/2026

💬 OpinionIdeas & Deep AnalysisModels & Research

Key Points

  • The paper proposes EGREFINE to improve Text-to-SQL by refining database schema names (e.g., ambiguous or inconsistent columns) rather than only fixing errors after generation.
  • It formulates schema refinement as a constrained optimization problem that maximizes downstream Text-to-SQL execution accuracy while preserving query equivalence using database views.
  • EGRefine uses a four-phase pipeline (ambiguous-column screening, context-aware candidate name generation, execution-grounded verification, and non-destructive SQL view materialization) to keep refinements safe.
  • The method includes two key guarantees: column-local non-degradation via conservative verification and database-level query equivalence via view-based materialization.
  • Experiments on degraded, real-world, and enterprise benchmarks show accuracy recovery when feasible, correct abstention when tasks exceed current Text-to-SQL limits, and “refine-once, serve-many” transfer across model families; code and data are released publicly.

Abstract

Text-to-SQL enables non-expert users to query databases in natural language, yet real-world schemas often suffer from ambiguous, abbreviated, or inconsistent naming conventions that degrade model accuracy. Existing approaches treat schemas as fixed and address errors downstream. In this paper, we frame schema refinement as a constrained optimization problem: find a renaming function that maximizes downstream Text-to-SQL execution accuracy while preserving query equivalence through database views. We analyze the computational hardness of this problem, which motivates a column-wise greedy decomposition, and instantiate it as EGRefine: a four-phase pipeline that screens ambiguous columns, generates context-aware candidate names, verifies them through execution-grounded feedback, and materializes the result as non-destructive SQL views. The pipeline carries two structural properties: column-local non-degradation, ensured by the conservative selection rule in the verification phase, and database-level query equivalence, ensured by the view-based materialization phase. Together they make the resulting refinement safe by construction at the column level, with cross-column and prompt-level interactions handled empirically rather than analytically. Across controlled schema-degradation, real-world, and enterprise benchmarks, EGRefine recovers accuracy lost to schema naming noise where applicable and correctly abstains where the underlying task exceeds current Text-to-SQL capabilities, with refined schemas transferring across model families to enable refine-once, serve-many-models deployment. Code and data are publicly available at https://github.com/ai-jiaqian/EGRefine.