Query Fingerprints or Literal Text Diffs: A Debate for Agent SQL Regression
A Tuesday review queue held three agent rewrites of the same reporting query, each formatted differently and each carrying a new bind value. The text diff looked noisy, the join graph looked unchanged, and the reviewer had twelve minutes before a freeze window. None of the candidates touched writes, yet one rewrite moved a date filter from orders.created_at onto a denormalized snapshot column.…
A debate rages over whether agent-written SQL queries should be evaluated based on their fingerprint or literal text differences. The article presents a two-sided argument with supporting evidence and a decision rule. The key points are:
1. Agent-written SQL often changes formatting, such as whitespace, alias names, literal formatting, and CTE labels, while preserving the join graph and predicates. This makes raw text comparison unreliable for regression gates.
2. Fingerprint comparison focuses on the underlying workload identity, stripping literals, comments, and whitespace. Equivalent restyles result in green CI tests, but join, filter, or projection changes cause a fingerprint mismatch and CI failure. However, this approach loses information about specific literals.
3. Literal text diff comparison ensures every changed character represents a potential new table, broader predicate, or function with different volatility. git diff on sqlfmt output is simple, understandable for compliance, and does not rely on a maintainable normalizer. However, this approach generates noise from formatting differences and struggles with bind-parameter style.
4. The article proposes a dual-gate fixture that stores a golden fingerprint and a canonical text file. The CI system can then apply different rules per query class using distinct exit codes. The fixture is labeled "unexecuted" until a controlled replica loads the schema.
In summary, the debate centers on whether to normalize SQL to a fingerprint for identity verification or keep literal text diffs to ensure changes are intentional. Both approaches have their merits and drawbacks, and a dual-gate solution may provide a balanced approach.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
