The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
| Version | Location | Description | Submitted by | Date submitted |
|---|---|---|---|---|
| Page 59 example 2-22, 2-23 |
Docstring type comments and their formatting as the one in Example 2-22 are not carried over to the documentation by dbt when running `docs generate`. Only the comments placed in the yml files are. |
Anonymous | Jul 14, 2024 | |
| Mobi | Page 63 CREATE TABLE books |
Missing a comma after summary VARCHAR(255) |
Francisco Galan | May 23, 2024 |
| Mobi | Page 64 CREATE TABLE publishes |
After the "REFERENCES...", it should be the "authors" table, with an "s", rather than "author" |
Francisco Galan | May 23, 2024 |
| Printed | Page 172 Last sentence of the second paragraph from the last above Example 4-7 |
Seems like a leftover fragment that was refactored into the last paragraph. Removing the sentence “even using dbt Cloud … with BigQuery” is recommended. |
Anonymous | Nov 20, 2024 |
| Printed | Page 226 2nd paragraph |
"Since, in this case, you will not have an actual materialization in your data platform, look at the dim_product compiled code." I beleive 'dim_product' should be 'dim_customer' - changing the materialization of stg_jaffle_shop_customers model to ephemeral will affect the downstream dim_product compiled code in the 'dim_customer' model. |
James Shepard | Nov 24, 2025 |