• our default build command is `dbt build --exclude "resource_type:seed" because seeds are depended on as a source, and running a regular build will create a race condition where some models beat their source seeds into the warehouse and cause failing tests

Is this because there are models whose dependencies are not being forced? Wouldn't it be better to force the dependency than babysit which nodes get built outside of dbt itself?

• our default build command is `dbt build --exclude "resource_type:seed" because seeds are depended on as a source, and running a regular build will create a race condition where some models beat their source seeds into the warehouse and cause failing tests

Is this because there are models whose dependencies are not being forced? Wouldn't it be better to force the dependency than babysit which nodes get built outside of dbt itself?

so @joellabes seeds run in parallel with everything else, if a source is pointed at a seed's output, and the seed is...seeding into the db still, bad stuff happens. there are no models to force the deps on, as they're sources rather than models. the Big Fix would be if seeds were treated as a proper part of the DAG, which there's an issue for and i've brought up with Doug and Jerco. i think that would make a lot of sense.

i have an alternative fix i'm toying with i'll send you as a Loom, would be interested in your thoughts on it, but it's more of a tradeoff than a fix.

Wouldn't this work?

#seeds/my_seed.csv
id,name
1,winnie
2,joel

#models/sources.yml
sources:
  - name: seeds
    tables: 
        - name: my_seed
          # etc

-- models/stg_my_seed.sql

-- depends_on: {{ ref('my_seed') }}
with seed as (
  select * from {{ source('seeds', 'my_seed') }}
)
-- etc

Maybe not a good idea as I write it out if this is meant to be a best practice demo

@joellabes oh yea i think you're right that should work, but yea maybe not ideal for beginners 🤔 hadn't thought of that though