Database
MoL-SQL: A Controlled Benchmark for Mixture-of-Language Text-to-SQL
arXiv cs.DB0 views
arXiv:2611.22333v1 Announce Type: new Abstract: Text-to-SQL systems are usually built and evaluated under a monolingual assumption, yet in international applications users often query databases stored in a different language. Existing multilingual benchmarks mostly translate only the question without aligning schema and value entities, so they can neither locate the source of an accuracy drop nor rule out translation errors. Hence, we introduce MoL-SQL, a benchmark for mixture-of-language Text-to-SQL that switches the languages of the question, schema, and stored values independently while keeping each task fixed, and grades every cross-lingual entity mapping into four difficulty levels. We migrate five Text-to-SQL benchmarks of different domains and source languages through a unified alignment pipeline that builds a shared cross-lingual entity map, migrates each database with its constraints, rewrites the gold SQL under execution-equivalence checks, and regenerates the question from the verified SQL, keeping all language versions of a task aligned in entities, intent, and execution result. MoL-SQL provides two splits: MoL-Full (16,892 samples) for overall evaluation and MoL-Cube (3,840 samples) covering every language combination to isolate question, schema, and value effects. Experiments with eight LLMs and four families of Text-to-SQL methods show that schema and value languages have distinct effects, with stored values costing up to 23 points, and that these effects mainly stem from cross-lingual entity mapping. Neither question translation nor additional reasoning narrows the value gap, whereas access to target-database values substantially reduces it, indicating that mixture-of-language Text-to-SQL benefits most from language-aware context grounding.
Source:https://arxiv.org/abs/2611.22333PreviousPelorus: Warped-Product Graph Indexing for Hyperbolic Vector SearchNextErrpedia: Is Your Exact $k$-NN Vector Search Really Exact?
Related posts
A Practical Stack Checklist for Small-Business Web Apps (Next.js, Node.js, SQL or MongoDB)
0dev.to Node

In an audit, a green test means the bug is real
0dev.to Testing
Fix Go Goroutine Leaks & Scale ClickHouse Monoliths
0dev.to Go
96 rows out of 47,114: when 92% of your joins return nothing and 97% of the rest return the wrong match
0dev.to Database
Device-Centric Cooperative Floor-Level Estimation under Sparse Anchor Deployment for Construction-Site Applications
0arXiv eess.SP
Lightfoot: Graph Retrieval-Augmented Generation with Exact, Model-Free Document Deletion
0arXiv cs.IR