REVIEW 2 cited by
SQLCritic: Correcting Text-to-SQL Generation via Clause-wise Critic
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
Signed reviews
abstract
Existing refinement methods in LLM-based Text-to-SQL systems exhibit limited effectiveness. They often introduce new errors during the self-correction process and fail to detect and correct semantic inaccuracies. To address these gaps, we first introduce a clause-wise critique generation task along with a benchmark, SQLCriticBench, which performs fine-grained error localization including both syntax and semantic errors at the clause level. Furthermore, we introduce a variant of DPO for training our SQLCritic model, where the $\beta$ coefficient is adaptively changed according to the clause-level inconsistencies between the preferred and dispreferred critiques. We also propose an automatically training dataset curation pipeline which annotate clause-wise critique at scale in a cost-effective way. Experiments demonstrate that the SQLCritic model significantly improves SQL accuracy on the BIRD and Spider datasets, and the results on SQLCriticBench further reveals its superior critique capabilities compared to existing models.
Forward citations
Cited by 2 Pith papers
-
ReEx-SQL: Reasoning with Execution-Aware Reinforcement Learning for Text-to-SQL
An execution-aware reinforcement learning framework that interleaves intermediate SQL execution into the reasoning path improves text-to-SQL accuracy on Spider and BIRD at the 7B scale.
-
Knowing When to Stop: Predicting Execution-Consistency Convergence in Text-to-SQL
Learned 1-D predictors of execution-consistency convergence stop Text-to-SQL sampling adaptively, beating fixed budgets and a Beta-Bernoulli rule on BIRD and two customer sets.
Discussion (0). Continue with ORCID to comment.