From the MotherDuck Slack, we had a user run into issues when they set their path to be md:?token=... and their database to motherduck_jaffles, which led to an inconsistency between what the DuckDB connection thought the default database was (my_db) and what dbt-duckdb thought the default database was (motherduck_jaffles) and weird behavior (e.g., dbt seed successfully creating the database tables but then failing to load them.) The fix was simply to adjust the path to be md:motherduck_jaffles?token=... so as to make the default database consistent.
We should detect these inconsistencies when parsing the DuckDBCredentials and throw an error since they can only cause mischief/confusion.
From the MotherDuck Slack, we had a user run into issues when they set their path to be
md:?token=...and their database tomotherduck_jaffles, which led to an inconsistency between what the DuckDB connection thought the default database was (my_db) and what dbt-duckdb thought the default database was (motherduck_jaffles) and weird behavior (e.g.,dbt seedsuccessfully creating the database tables but then failing to load them.) The fix was simply to adjust the path to bemd:motherduck_jaffles?token=...so as to make the default database consistent.We should detect these inconsistencies when parsing the
DuckDBCredentialsand throw an error since they can only cause mischief/confusion.