Google researchers push for "pipe" syntax in SQL to tame sprawling queries

Google Research has published a paper titled "SQL Has Problems. We Can Fix Them: Pipe Syntax In SQL (2024)," and it has been reported that the authors propose adding a pipe-style composition operator to SQL. Short version: treat SQL more like a data pipeline. Think Unix pipes, but for relational queries — chain transformations instead of nesting them into ever-deeper haystacks. It reads like an invitation to make SQL less of a contortion contest and more of a readable workflow.

What the paper argues

The paper allegedly frames the change as a fix for real developer pain: long nested subqueries, confusing WITH chains, and brittle query composition that makes debugging painful. It has been reported that the proposed pipe syntax aims to improve composability and readability, letting teams stitch together transformations in a linear, modular way. Google Research regularly publishes and open-sources tool ideas; the authors position this work as part of a broader push to advance database ergonomics and reduce friction for large-scale data engineering.

Why it matters — and what could get in the way

Why should anyone care? Because SQL is everywhere. Data analysts, product teams, and ML pipelines all rely on it. A cleaner, pipe-first syntax could be a genuine quality-of-life win — imagine fewer parentheses, clearer intent, and easier reuse of intermediate steps. But standards, tooling, and backward compatibility are real hurdles. Will the SQL ecosystem bend? Will vendors adopt it? Those questions remain. For now, the paper is a provocative nudge: SQL doesn’t have to be stuck in its 1970s robe. Developers who’ve wrestled with monstrous queries might finally exhale — or at least reach for the duct tape with more confidence.

Sources: research.google, Lobsters