Skip to content

Latest commit

 

History

History
32 lines (23 loc) · 2.22 KB

File metadata and controls

32 lines (23 loc) · 2.22 KB

dbt Style Guide

Language requirements

  • Every column description should be in German

SQL style guide

These SQL style choices should be asserted with a .sqlfluff configuration file and linting in CI jobs.

  • DO NOT OPTIMIZE FOR FEWER LINES OF CODE.

    New lines are cheap, brain time is expensive; new lines should be used within reason to produce code that is easily read.

  • Use trailing commas

  • Indents should use four spaces.

Model Layers

  • Only models in staging should select from sources

  • Models not within the silver/staging folder should select from refs.

  • The following are the DAG stages that we will use:

    Common
    file_prefix / dag_stage Typically found in description
    seed_ /seeds
  • Indicates a data set created from dbt seed.
  • stg_ /models/silver/staging
  • Indicates a data set that is being cleaned and standardized.
  • In absence of a base_ layer, it represents the 1:1 relationship between the bronze source and first layer of models.
  • int_ /models/silver/intermediate
  • Indicates a logical step towards creating a final / gold data set.
  • Typically used for:
    • Breaking up a very large fct_ or dim_ model into smaller pieces to reduce complexity
    • Creating a reusable data set to reference in multiple downstream fct_ and dim_ models
    dim_ /models/gold
  • Flags data which is used to describe an entity.
  • Indicates a final data which is robust, versatile, and ready for consumption.
  • fct_ /models/gold
  • Flags data which is in the form of numeric facts observed during measurement events.
  • Indicates a final data which is robust, versatile, and ready for consumption.