diff --git a/code_thingies/dbtlearn/README.md b/code_thingies/dbtlearn/README.md index 343ff58..d470985 100644 --- a/code_thingies/dbtlearn/README.md +++ b/code_thingies/dbtlearn/README.md @@ -27,6 +27,8 @@ Once you have set this up and the database as well, you can run `dbt debug` to e You should also delete the lines under the `dbtlearn` key in the `dbt_project.yml` file. +Also delete the contents of the `models` folder. + # DBT noisy things below diff --git a/code_thingies/dbtlearn/models/example/my_first_dbt_model.sql b/code_thingies/dbtlearn/models/example/my_first_dbt_model.sql deleted file mode 100644 index f31a12d..0000000 --- a/code_thingies/dbtlearn/models/example/my_first_dbt_model.sql +++ /dev/null @@ -1,27 +0,0 @@ - -/* - Welcome to your first dbt model! - Did you know that you can also configure models directly within SQL files? - This will override configurations stated in dbt_project.yml - - Try changing "table" to "view" below -*/ - -{{ config(materialized='table') }} - -with source_data as ( - - select 1 as id - union all - select null as id - -) - -select * -from source_data - -/* - Uncomment the line below to remove records with null `id` values -*/ - --- where id is not null diff --git a/code_thingies/dbtlearn/models/example/my_second_dbt_model.sql b/code_thingies/dbtlearn/models/example/my_second_dbt_model.sql deleted file mode 100644 index c91f879..0000000 --- a/code_thingies/dbtlearn/models/example/my_second_dbt_model.sql +++ /dev/null @@ -1,6 +0,0 @@ - --- Use the `ref` function to select from other models - -select * -from {{ ref('my_first_dbt_model') }} -where id = 1 diff --git a/code_thingies/dbtlearn/models/example/schema.yml b/code_thingies/dbtlearn/models/example/schema.yml deleted file mode 100644 index 2a53081..0000000 --- a/code_thingies/dbtlearn/models/example/schema.yml +++ /dev/null @@ -1,21 +0,0 @@ - -version: 2 - -models: - - name: my_first_dbt_model - description: "A starter dbt model" - columns: - - name: id - description: "The primary key for this table" - tests: - - unique - - not_null - - - name: my_second_dbt_model - description: "A starter dbt model" - columns: - - name: id - description: "The primary key for this table" - tests: - - unique - - not_null diff --git a/images/dataflow_overview.png b/images/dataflow_overview.png new file mode 100644 index 0000000..10abfce Binary files /dev/null and b/images/dataflow_overview.png differ diff --git a/notes/1.md b/notes/sections1-7.md similarity index 96% rename from notes/1.md rename to notes/sections1-7.md index a328a88..4e25c8a 100644 --- a/notes/1.md +++ b/notes/sections1-7.md @@ -103,4 +103,6 @@ dbt makes sense nowadays because the modern data stack makes transformations wit ## dbt project structure -- `dbt_project.yml`: header of the project, with stuff like versioning, the default profile for the project, the paths to different folders, etc. \ No newline at end of file +- `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) \ No newline at end of file