Replacing Training with Memory: Listwise Selection for Text-to-SQL

Yeonseok Jeong, Soyoung Yoon, Seongjun Lee, Seung-won Hwang

Seoul National University · KAIST

Published September 1, 2026 · on the feed September 3, 2026 · ▲ 2 · arXiv 2609.00834

Retrieval, memory & searchLLM training & RL Code arXiv ↗Hugging Face ↗

The abstract

Modern Text-to-SQL systems often follow generate-execute-select pipelines, generating multiple candidate queries then selecting the best one. Listwise selection, by jointly comparing multiple candidates, has been widely adopted, but fine-tuning listwise selectors is costly. We thus propose a fine-tuning-free listwise selector. We replace two major fine-tuning objectives with inference-time strategies: (1) learning selection criteria as ordering and (2) mitigating positional bias. First, we build reusable structured memories instead of learning selection behavior as model parameters. Given a question, MaP-SQL retrieves memories distilled from training data that encode how natural language maps to schema elements, SQL operations, and expected outputs. These memories serve as explicit decision criteria for evaluating candidates in a listwise manner. Second, to mitigate ordering bias of listwise selectors, we aggregate rankings across multiple input permutations, with inference cost optimized by execution results and pointwise scoring. Our approach improves selection accuracy while maintaining efficiency and compatibility with existing large language models. Across Text-to-SQL benchmarks, it produces more stable selection without fine-tuning and fewer unnecessary comparisons than existing methods. On BIRD-dev, it outperforms the previous state-of-the-art selector-based method R^3-SQL by 2.02 execution accuracy points on average using the same candidate sets, with 2.92x fewer tokens.

The Brief

2:26

A short podcast summary of the paper. Written and voiced by AI.

Transcript

Replacing Training with Memory. Listwise Selection for Text-to-SQL. By Yeonseok Jeong and three others, from Seoul National University and KAIST. Published on the first of September. Its code repository is public and real: nineteen source files.

Modern Text-to-SQL systems often work as a pipeline of three steps: generate several candidate queries, execute them, then select the best one. Listwise selection, where a model compares several candidates jointly instead of scoring each alone, has been widely adopted for that last step. The catch is training. Fine-tuning a listwise selector is costly, and the fine-tuning is doing two jobs at once. It teaches the model which criteria to order candidates by, and it teaches the model to resist positional bias, the pull toward a candidate simply because of where it sits in the list.

MaP-SQL keeps listwise selection and drops the fine-tuning. Each of those two training objectives is replaced with a strategy that runs at inference time. Selection criteria, instead of being learned into model parameters, are kept as reusable structured memories. Ordering bias, instead of being trained away, is averaged out.

The memories are distilled from training data. Given a question, MaP-SQL retrieves the ones that encode how natural language maps to schema elements, to SQL operations, and to expected outputs. Those memories then serve as explicit decision criteria when the model evaluates candidates side by side. For ordering bias, the method aggregates rankings across multiple permutations of the input, so that no single placement decides the outcome. Running many permutations could get expensive, and the abstract says that cost is kept down using execution results and pointwise scoring.

Across Text-to-SQL benchmarks, the approach produces more stable selection without fine-tuning, and makes fewer unnecessary comparisons than existing methods. The headline result is on BIRD-dev. Using the same candidate sets, it outperforms the previous state-of-the-art selector-based method by two point zero two execution accuracy points on average. It does so while using two point nine two times fewer tokens. The authors also stress that it stays efficient and compatible with existing large language models.

The title states the trade plainly. What a fine-tuned selector would have absorbed into its weights is here written down as memory that can be retrieved, and what training would have suppressed is handled by asking the same question in several orders. Selection accuracy goes up, and the selector itself never has to be trained.

Paper Quest · 7 chapters · about 41 min

Play this paper

Learn it by doing: make the calls the authors made, guess the result before you see it, and defend it in a viva graded on your own words. Chapter 1 is right here.

Chapter 1 🧩 · The problem

The selector works, but training it costs too much. That's the wall.

Your Text-to-SQL system writes several candidate queries for each question, runs them, and must pick the best. Comparing all candidates together in one prompt works well.

The road ahead

  1. 1 · The problem ~7 min Comparing all candidate SQL queries together picks well, but training a model to do it is costly and the model is swayed by list position.
  2. 2 · What came before ~3 min
  3. 3 · The key idea ~9 min Replace the two jobs of fine-tuning with inference-time tricks: retrieved memories give the criteria, and averaging rankings over several orders reduces position bias.
  4. 4 · Choose your own research ~3 min
  5. 5 · Build the method ~8 min Generate candidates, execute them, rank them in windows with retrieved memories as criteria, then aggregate rankings over several group-based orders.
  6. 6 · The experiment ~6 min You’ll guess: On BIRD-dev, against the previous best selector-based method R^3-SQL, how many times fewer tokens did MaP-SQL use?
  7. 7 · The viva ~5 min Three questions from the examiners, answered in your own words. Win it for the paper’s trophy.
Join free to play the whole quest ›

Free, with Google or an email address. Your stars and progress are kept.

KipQuest: the day’s AI research, as podcasts and quests. All papers Android app Privacy Contact Episodes are written and voiced by AI from each paper. Summaries can contain mistakes: the paper is the source.