SQL in 7 Days (Alex Bolenok)（Z-Library）

# SQL in 7 Days: A Quick Crash Course in Manipulating Data, Databases Operations, Writing Analytical Queries, and Server-side Programming ## 【One-Line Pitch】 A fast-paced, practical crash course that takes you from zero to writing real analytical SQL queries in a week, using PostgreSQL as the reference database. Ideal for developers, data analysts, and IT professionals who need to get productive with relational databases quickly without wading through a 900-page textbook. ## 【Book Arc】 - **Opening (~0%–9%)**: Sets expectations — this is a breadth-over-depth crash course using PostgreSQL 13.2 as the reference implementation. The author explains why SQL varies across vendors, introduces the ANSI standard, and tells you how to run the book's code via a Docker image. The tone is conversational and history-aware, not a dry reference manual. - **Early (~16%–28%)**: Lays the conceptual foundation. The author walks through the pre-relational world (hierarchical databases) through a fictional story about "Denis," a 1960s programmer drowning in hard-coded data references. This sets up the core insight: the relational model's revolutionary idea is that relationships between data are themselves data, not pointers or paths. - **Early (~34%–47%)**: Deepens the relational model with concrete analogies — like Elsie's vacuum cleaner inventory system — to explain why records should be referenced by stable, embedded identifiers rather than physical positions. The "separation of concerns" principle (defining data vs. locating it) is the key takeaway here. - **Middle (~38%–53%)**: Moves from theory to the mechanics of the relational model: tuples, tables, records, strict typing, and the crucial idea that row order doesn't matter. The author emphasizes that relationships are defined at query time, not storage time — the true "killer feature" of relational databases. - **Late (beyond ~53%)**: The table of contents reveals the remaining structure: INSERT and data loading, basic SELECT queries (filters, joins, NULL logic, semi-joins, anti-joins), advanced queries (aggregation, window functions, CTEs, recursive queries, JSON), and data organization (entity-relationship modeling, constraints, normalization). The excerpts do not cover these chapters in detail, but the progression is clear: fundamentals → query mechanics → advanced analytics → data design. ## 【Key Takeaways】 - **The relational model's core innovation is that relationships are data, not pointers** (Early): Instead of hard-coding references between records (as in hierarchical databases), you embed stable identifiers directly in the data. This decouples data storage from data access, making systems far more flexible and maintainable. - **Row order in a table is meaningless** (Middle): In the relational model, swapping two rows changes nothing. This is a radical departure from file-based systems and is the foundation for set-based thinking in SQL — you operate on whole sets of data, not sequential records. - **SQL is declarative, not procedural** (Early): You describe *what* data you want, not *how* to get it. The database engine figures out the execution plan. This is both SQL's greatest strength (productivity) and a common source of confusion for programmers used to imperative languages. - **The relational model emerged as a response to real pain** (Early): The "Denis" story illustrates the nightmare of maintaining hard-coded hierarchies — every new report required rewriting access paths, updating references, and debugging spaghetti code. Codd's 1970 paper was a direct answer to this crisis. - **Separation of concerns is the design principle that makes relational databases work** (Middle): Defining data (what it is) is separate from locating data (where it is). Like Elsie's inventory numbers stenciled on equipment, records should carry their own stable identifiers, freeing the database from tracking physical positions. - **PostgreSQL is the reference implementation, but SQL is portable with caveats** (Opening): The book uses PostgreSQL 13.2, and while most code is ANSI-standard, vendor extensions exist. The author warns that other databases (MySQL, SQL Server) may require minor tweaks — a practical reality every SQL developer must accept. - **The book favors breadth over depth** (Opening): It's a crash course, not an encyclopedia. You'll learn many aspects of SQL quickly, but you won't get exhaustive detail on any single topic. This is a deliberate trade-off for a 7-day learning sprint. ## 【Reading Tips】 - **Skim the historical narrative in the early chapters** (0%–28%): The "Denis" and "Elsie" stories are engaging but not essential for writing SQL. Read them once for context, then move on — the conceptual payoff (relationships as data) matters more than the storytelling. - **Deep-read the relational model explanation** (28%–47%): This is the intellectual core of the book. Understanding *why* the relational model works the way it does will make every subsequent SQL concept (joins, keys, normalization) click into place. Don't rush this section. - **Use the Docker image for hands-on practice** (Opening): The book provides a ready-made database environment. Don't just read the queries — run them. SQL is a skill you learn by doing, and the 7-day structure assumes you're typing code alongside the text. - **Skip the front matter and publisher pages** (0%–16%): The copyright, piracy warnings, and author bio add nothing to your learning. Jump straight to the table of contents and Chapter 1. - **Treat the later chapters (queries, aggregation, normalization) as reference material**: Once you've internalized the relational model, the remaining chapters are best used as a practical guide to specific syntax and patterns. Skim when you need a refresher, deep-read when tackling a new concept like window functions or CTEs. ## 【Coverage Limits】 This guide synthesizes the book's conceptual foundation (relational model, SQL history, design principles) and overall structure. The excerpts do not cover the detailed syntax of INSERT, SELECT, joins, aggregation, window functions, or normalization — those chapters are listed in the table of contents but not excerpted in the source material. ##