Thingies

code_thingies/dbtlearn/models/mart/mart_fullmoon_reviews.sql

@@ -0,0 +1,27 @@
+{{
+    config(
+        materialized = 'table'
+    )
+}}
+
+WITH fact_reviews AS (
+    SELECT *
+    FROM
+        {{ ref('fact_reviews') }}
+),
+full_moon_dates AS (
+    SELECT *
+    FROM
+        {{ ref('seed_full_moon_dates')}}
+)
+
+SELECT
+    fr.*,
+    CASE
+        WHEN fm.full_moon_date IS NULL THEN 'not full moon'
+        ELSE 'full moon'
+    END AS is_full_moon
+FROM
+    fact_reviews fr
+    LEFT JOIN full_moon_dates fm
+    ON (fr.review_date::date) = (fm.full_moon_date + interval '1' day)

code_thingies/dbtlearn/models/sources.yml

@@ -0,0 +1,12 @@
+version: 2
+
+sources:
+  - name: airbnb
+    schema: raw
+    tables:
+      - name: listings
+        identifier: raw_listings
+      - name: hosts
+        identifier: raw_hosts
+      - name: reviews
+        identifier: raw_reviews

code_thingies/dbtlearn/models/src/src_hosts.sql

@@ -1,6 +1,6 @@
 WITH raw_hosts AS (
 	SELECT *
-	FROM raw.raw_hosts
+	FROM {{ source ('airbnb', 'hosts')}}
 )
 SELECT
 	id as host_id,

code_thingies/dbtlearn/models/src/src_listings.sql

@@ -1,6 +1,6 @@
 WITH raw_listings AS (
 	SELECT *
-	FROM raw.raw_listings
+	FROM {{ source ('airbnb', 'listings')}}
 )
 SELECT
 	id AS listing_id,

code_thingies/dbtlearn/models/src/src_reviews.sql

@@ -1,6 +1,6 @@
 WITH raw_reviews AS (
 	SELECT *
-	FROM raw.raw_reviews
+	FROM  {{ source ('airbnb', 'reviews')}}
 )
 SELECT
 	listing_id,

notes/8.md

@@ -42,4 +42,9 @@ WHERE
 
 Bear in mind that how to define the strategy to determine what should be loaded is up to the engineer. Any SQL can be placed within the `if is_incremental()` block. In the example above, we have a date field that easily signals what's the most recent date the table has currently seen.
 
-## 
+## Sources and seeds
+
+Seeds are local files that you upload to a DWH from dbt. You place them as CSVs in the `seeds` folder.
+
+
+Sources are an abstraction layer on top of the input tables. They are not strictly necessary, but can help make the project more structured. To create sources, you create a `sources.yml` file and place it in the `models` dir.

notes/sections1-7.md

@@ -106,11 +106,3 @@ dbt makes sense nowadays because the modern data stack makes transformations wit
 - `dbt_project.yml`: header of the project, with stuff like versioning, the default profile for the project, the paths to different folders, etc.
 
 This is a pic of the data flow we are going to build: ![img.png](../images/dataflow_overview.png)
-
-## Sources and seeds
-
-Seeds are local files that you upload to a DWH from dbt. You place them as CSVs in the `seeds` folder.
-
-
-Sources are an abstraction layer on top of the input tables.
-