Table Writes

Missing Keys Do Not Change Rows

Missing update/delete keys are rejected visibly.

highlighted = computed this step

Missing keys do not change rows

UPDATE and DELETE need a matching key.

missing key is rejected\text{missing key is rejected}

Reject missing keys

Rejected writes are 2, and final rows stay 3.

rejected=2\text{rejected}=2

Write examples are tiny finite row modifications; SQL dialects, transactions, constraints beyond the visible key, triggers, indexes, concurrency, performance, and product behavior are out of scope.

Missing keys do not change rows: base tableidnamepoints1Ada102Ben203Cy15 writes in orderstepkindkeydetail0update9{points:1}1delete8delete row write resultsstepkindkeystatusreasonbeforeafter0update9rejectedmissing_key331delete8rejectedmissing_key33 final tableidnamepoints1Ada102Ben203Cy15 write factsfactvaluebaseRowCount3writeCount2appliedCount0rejectedCount2finalRowCount3keyColumnidrowOrderkey

Read each reason

Both write results say missing_key, so no row is updated or deleted.

no matching row\text{no matching row}

Summary

The model does not invent a row to make the write succeed.

fail closed result\text{fail closed result}