Saved Queries

Materialized Copy Can Be Stale

A stored copy can differ from the current view output.

highlighted = computed this step

Materialized copy can be stale

A materialized copy is stored output. If the base table changes, the stored copy can lag behind.

stored copy can lag\text{stored copy can lag}

Compare current and stored

The current view has 1 row, and the stale flag is yes.

current rows=1\text{current rows}=1

View examples are tiny finite saved-query outputs; SQL dialects, optimizers, security, updatability, materialized-view strategy, performance, and maintenance advice are out of scope.

Materialized copy can be stale: base tableidstatustotal1closed502closed203open80 view column mappingsourceoutputididtotaltotal view filteropcolumnvalueeqstatusopen source rows usedbaseRow2 current view outputidtotal380 materialized copyidtotal150370 view factsfactvaluebaseRowCount3sourceRowCount1rowCount1columnCount2staleyeshasFilteryeshasAliasesnohasMaterializedCopyyes

Read both tables

The current output and materialized copy are both rendered, so the mismatch is visible.

visible mismatch\text{visible mismatch}

Summary

This shows finite stored-copy behavior, not materialized-view maintenance advice.

copy may differ\text{copy may differ}