Prepping the dbt-duckdb tests to pass under the next release of DuckDB #166
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Trying a new thing where I test out dbt-duckdb against the next release of DuckDB about a week-or-so before it comes out so I can get ahead of any bug fixes or updates I need in dbt-duckdb instead of having to scramble the day of the release to get stuff fixed.
Two things I needed to fix when I ran against
0.7.2-dev
:integer_division
setting to true, which I am doing here b/c some of the dbt tests fail without this setting in place.