Use is_first_insert instead

Author: VaggelisD

sqlmesh/core/snapshot/evaluator.py

@@ -2284,11 +2284,11 @@ def insert(
     ) -> None:
         # We should always recreate materialized views across supported engines (Snowflake, BigQuery etc) because
         # if upstream tables were recreated (e.g FULL models), the MVs would be silently invalidated.
-        # The only exception to that rule is RisingWave, which doesn't support CREATE OR REPLACE, so upstream 
+        # The only exception to that rule is RisingWave, which doesn't support CREATE OR REPLACE, so upstream
         # models don't recreate their physical tables for the MVs to be invalidated.
-        # However, even for RW we still want to recreate MVs to avoid stale references  
+        # However, even for RW we still want to recreate MVs to avoid stale references
         is_materialized_view = self._is_materialized_view(model)
-        must_recreate_view = not self.adapter.HAS_VIEW_BINDING or is_materialized_view
+        must_recreate_view = not self.adapter.HAS_VIEW_BINDING or is_first_insert
 
         if self.adapter.table_exists(table_name) and not must_recreate_view:
             logger.info("Skipping creation of the view '%s'", table_name)

tests/core/engine_adapter/integration/test_integration.py

@@ -3772,7 +3772,7 @@ def test_materialized_view_evaluation(ctx: TestContext, mocker: MockerFixture):
             )
         )
     )
-    
+
     def _assert_mview_value(value: int):
         df = adapter.fetchdf(f"SELECT * FROM {mview_name.sql(dialect=dialect)}")
         assert df["col"][0] == value
@@ -3794,5 +3794,4 @@ def _assert_mview_value(value: int):
 
         assert any("Replacing view" in call[0][0] for call in mock_logger.call_args_list)
 
-
-    _assert_mview_value(value=2)
+    _assert_mview_value(value=2)