Description
An AI agent will hand you SQL that runs and returns a plausible-looking result set, and is quietly wrong: a join that fans out and double-counts every total, a NOT IN that silently returns nothing because one value was NULL, an index it proudly added that the query can never use, a GROUP BY that disagrees with the join beneath it, a migration that will lock a million-row table the moment it hits production, a query built by string concatenation that is one input away from an injection. The database waves almost all of it through, because returning rows proves the query parsed and executed, not that the result is correct, the plan is sane, or the data is safe. Syntax tutorials do not help here, you are not the one typing the query. What you lack is the reviewer’s mental model: what the database is actually doing underneath the query, so you can look at a diff and know whether to ship it or send it back.
This book trains you to be the reviewer of vibe-coded SQL, not to memorize the syntax. It starts from a different premise than every other SQL book: the agent writes the queries, and your edge is understanding what the database really does so you can review it with judgment the engine does not have. You’ll learn why a relational table is a set and why thinking in sets is the whole game, the order the engine actually evaluates a query in, how joins and indexes really execute and when an index is useless, the three-valued logic that makes NULL the most common silent-wrong-result bug in SQL, how to read a query plan as the ground truth the SQL hides, and how transactions, isolation, and migrations behave under real concurrency and scale, and you’ll learn all of it the way a reviewer needs it: by reading real queries the agent would generate and deciding what is good, what is plausible-but-dangerous, and what to push back on. The progression moves from reviewing a single query and a single index, to reviewing a schema and its constraints, to reviewing how the whole workload behaves under load and where it will fall over. There is almost no syntax drill here, and a great deal about the relational model, query execution, data integrity, and the specific ways an agent’s SQL goes wrong. For engineers who are going to vibe-code SQL either way and want to be the one who catches what the model missed.
Who this book is for
This book is for: engineers who have decided to let an AI agent write their SQL, schema, and migrations (vibe-coding) and now own the part the agent cannot, which is judging whether the queries are correct, fast, and safe against real data, and who refuse to spend months grinding syntax tutorials to get there.
The framework you’ll learn
The 5 Steps to Becoming the SQL Reviewer AI Can’t Replace. The review discipline that turns an engineer who trusts the SQL an agent hands them into the one who catches what it got wrong. The database returning rows only proves the query ran, not that it is correct, fast, or safe. Learn to read what the engine actually does underneath the result, at every altitude from a single query to a schema to a workload under load, and become the reviewer the agent cannot replace.
- Learn to see what the first read hides
- Read underneath a single query
- Read the schema that lets bad data in
- Read the workload under real load
- Prove the verdict and own the review
What you’ll walk away with
- Chapter 1: The query I trusted that made me look wrong in the meeting
- Chapter 2: Why is my data split across tables, and how do I put it back together?
- Chapter 3: So what actually happens when I run a query?
- Chapter 4: I joined two tables and my totals doubled. What happened?
- Chapter 5: Why is my filter dropping rows that should be there?
- Chapter 6: It works, but it’s painfully slow. How do I make it fast?
- Chapter 7: Why does this query take forever, and how do I find out?
- Chapter 8: The dashboard numbers don’t add up. Where did the math break?
- Chapter 9: How do I answer a hard question without drowning in SQL?
- Chapter 10: How do I stop bad data from getting in and ruining everything later?
- Chapter 11: Two people save at the same time and something’s lost. How do I stop it?
- Chapter 12: I need to change the live database without taking the site down
- Chapter 13: How do I know my query meets the company’s security rules?
- Chapter 14: I’ve got my query. How do I make sure it’s right without breaking anything?
- Chapter 15: How I became the reviewer the agent can’t replace
