Use Tuple instead.

dbt-labs · Feb 27, 2024 · 170be02 · 170be02
1 parent 0b81eb8
commit 170be02
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/core/dbt/adapters/base/relation.py b/core/dbt/adapters/base/relation.py
@@ -41,13 +41,13 @@ class BaseRelation(FakeAPIObject, Hashable):
     # adding a relation type here also requires defining the associated rename macro
     # e.g. adding RelationType.View in dbt-postgres requires that you define:
     # include/postgres/macros/relations/view/rename.sql::postgres__get_rename_view_sql()
-    renameable_relations: SerializableIterable = field(default_factory=lambda: FrozenSet())
+    renameable_relations: SerializableIterable = field(default_factory=lambda: Tuple())
 
     # register relation types that are atomically replaceable, e.g. they have "create or replace" syntax
     # adding a relation type here also requires defining the associated replace macro
     # e.g. adding RelationType.View in dbt-postgres requires that you define:
     # include/postgres/macros/relations/view/replace.sql::postgres__get_replace_view_sql()
-    replaceable_relations: SerializableIterable = field(default_factory=lambda: FrozenSet())
+    replaceable_relations: SerializableIterable = field(default_factory=lambda: Tuple())
 
     def _is_exactish_match(self, field: ComponentName, value: str) -> bool:
         if self.dbt_created and self.quote_policy.get_part(field) is False: