Foreign key reference fails with "Table does not exist" in dbt-duckdb

[elisevansbbfc]

I’m running into an issue when trying to set up a simple pair of models with constraints defined in schema.yml. Even though random_model_2 builds successfully, random_model_1 fails with a runtime error saying the table does not exist.

Repo structure

models/random_model/ has 3 files:

schema.yml

version: 2

models:
  - name: random_model_2
    config:
      contract:
        enforced: true
    columns:
      - name: col
        data_type: int
        constraints:
          - type: primary_key
      - name: extra
        data_type: varchar

  - name: random_model_1
    config:
      contract:
        enforced: true
    columns:
      - name: col
        data_type: int
        constraints:
          - type: foreign_key
            expression: "elis_dev.random_model_2 (col)"
      - name: extra
        data_type: varchar

random_model_1.sql

-- depends_on: {{ ref("random_model_2") }}

select
    unnest([1, 1]) as col, unnest(['a', 'b']) as extra

random_model_2.sql

select
    unnest([1,2]) as col, unnest(['blah', 'blah']) as extra

When I run dbt run --select random_model I get the following error:

Failure in model random_model_1 (models/random_model/random_model_1.sql)
  Runtime Error in model random_model_1 (models/random_model/random_model_1.sql)
  Catalog Error: Table with name random_model_2 does not exist!
  Did you mean "dbname.elis_dev.random_model_2"?

Full logs:

16:23:38  1 of 2 OK created sql table model dbname.elis_dev.random_model_2
16:23:38  2 of 2 ERROR creating sql table model dbname.elis_dev.random_model_1
...
Catalog Error: Table with name random_model_2 does not exist!
Did you mean "dbname.elis_dev.random_model_2"?

Environment

python = "^3.11"
dbt-duckdb = "^1.9.2"

Logs show me that I'm running with dbt=1.10.10 and duckdb=1.9.4

profiles.yml

dbt_setup:
  outputs:
    dev:
      schema: elis_dev
      threads: 1
      type: duckdb
      attach:
        - path: "postgresql://{{ env_var('DB_USER') }}:{{ env_var('DB_PASSWORD') }}@{{ env_var('DB_HOST') }}:{{ env_var('DB_PORT') }}/dbname"
          type: postgres
          alias: dbname

What I'm expecting here is that random_model_2 builds first, and then random_model_1 should successfully build and apply the foreign key constraint. But random_model_1 fails with a Catalog Error saying the table does not exist, even though random_model_2 exists in the same schema.

Is this a bug with how dbt-duckdb handles constraints in schema.yml, or am I misconfiguring something? Is it something to do with the Postgres attach? Is there any work around for this?