Prior to DuckDB 0.7.0, dbt-duckdb could actually work out-of-the-box with no path argument at all, since the default value of the path argument was :memory: and the only database supported was the default of "main". 0.7.0 changed that s.t. if there is no path supplied, the value of the database setting needs to be "memory" for everything to work correctly; this PR updates the code so that the old behavior of running in-memory DBs when the path is unspecified will work correctly in the new regime.
Prior to DuckDB 0.7.0, dbt-duckdb could actually work out-of-the-box with no
pathargument at all, since the default value of thepathargument was:memory:and the only database supported was the default of "main". 0.7.0 changed that s.t. if there is nopathsupplied, the value of thedatabasesetting needs to be "memory" for everything to work correctly; this PR updates the code so that the old behavior of running in-memory DBs when the path is unspecified will work correctly in the new regime.