v1.10.0rc1

[Benjamin-Knight]

What's Changed

• Modernize packaging: migrate setup.py to PEP 621 pyproject.toml by @joshmarkovic in Modernize packaging: migrate setup.py to PEP 621 pyproject.toml #645
• chore(dependabot): switch Dependabot to weekly and separate security by @axellpadilla in chore(dependabot): switch Dependabot to weekly and separate security #666
• UV usage by @Benjamin-Knight in UV usage #668
• Update adapter to dbt 1.10. by @Benjamin-Knight in Update adapter to dbt 1.10. #669
• Fix snapshot meta column name overrides on second run (Second run of dbt snapshot missing valid from/to columns #639). by @Benjamin-Knight in Fix snapshot meta column name overrides on second run (#639). #670
• Add opt-in native string type mappings via behaviour flag (dbt.type_string() compiles to varchar(8000) #626). by @Benjamin-Knight in Add opt-in native string type mappings via behaviour flag (#626). #671
• Add regression tests for connection-string port handling (Port is not being applied properly when using Windows Login with non-default port #496). by @Benjamin-Knight in Add regression tests for connection-string port handling (#496). #672
• Add DML table refresh method for table materializations (Table materialization rename-swap causes query failures under Read Committed Snapshot Isolation #641). by @Benjamin-Knight in Add DML table refresh method for table materializations (#641). #673
• Add regression tests for limit handling in test SQL generation (unique test on seed fails with "Invalid column name 'None'" in dbt-sqlserver 1.9.0 #638). by @Benjamin-Knight in Add regression tests for limit handling in test SQL generation (#638). #675
• Fix CTE detection with comments (Initial comment lines break empty_subquery_sql #621) by @Benjamin-Knight in Fix CTE detection with comments (#621) #676
• Fix reserved-keyword quoting in table-create DROP VIEW (Error on table materialization when using special schema name #619). by @Benjamin-Knight in Fix reserved-keyword quoting in table-create DROP VIEW (#619). #677
• Add TABLOCK hint to contract-enforced INSERT INTO (DBT Contracts Performance #640). by @Benjamin-Knight in Add TABLOCK hint to contract-enforced INSERT INTO (#640). #678
• [pre-commit.ci] pre-commit autoupdate by @pre-commit-ci[bot] in [pre-commit.ci] pre-commit autoupdate #412
• Update the catalog macros to support multiple databases by @Benjamin-Knight in Update the catalog macros to support multiple databases #603
• Fix: Handle view materialization alterations by @axellpadilla in Fix: Handle view materialization alterations #610
• Fix: Update model constraints functional test expectation for SQL Server contract INSERT semantics by @axellpadilla in fix: Update model constraints functional test expectation for SQL Server contract INSERT semantics #684
• Feat: add default schema concatenation flag support and update documentation by @axellpadilla in ✨ feat: add default schema concatenation flag support and update documentation #685
• Perf: make hot-path adapter catalog queries sargable by @joshmarkovic in perf: make hot-path adapter catalog queries sargable #686
• Update dbt-core dependency version range by @axellpadilla in Update dbt-core dependency version range #690
• Add query_options model config for SQL Server OPTION clauses (Max Recursion config property #613). by @Benjamin-Knight in Add query_options model config for SQL Server OPTION clauses (#613). #674
• Update SQL server relations to not require an alias by @Benjamin-Knight in Update SQL server relations to not require an alias #604
• Test tablock and query options interaction by @Benjamin-Knight in Test tablock and query options interaction #679
• Update changelog for v1.10.0 by @axellpadilla in Update changelog for v1.10.0 #693
• Improve environment setup and update dependencies for v1.10.0 by @axellpadilla in Improve environment setup and update dependencies for v1.10.0 #696

Full Changelog: v1.9.1...v1.10.0rc1

---

This discussion was created from the release v1.10.0rc1.

[joshmarkovic]

Works on my ~750 models :)

[joshmarkovic]

One 'issue' I'm having is that the new release is requiring dbt_readonly on all of my databases. Is this expected? I would assume it would use my profiles?

[Benjamin-Knight]

One 'issue' I'm having is that the new release is requiring dbt_readonly on all of my databases. Is this expected? I would assume it would use my profiles?

That's very unusual, the value dbt_readonly does not appear in the adapter anywhere that I can easily locate and none of the changes made affected the grants in anyway other than preserving them.

[axellpadilla]

Also can't relate nor find dbt_readonly anywhere on core or dbt-adapters package

[Benjamin-Knight]

Did you determine what the issue was?

[joshmarkovic]

TL;DR User error🤦

I have one database that is only used as 'sources' in my dbt deployment and never required a user/service account. However, the new released required the user to exist in that database as well.