Write failures and indirect effects
Inspect transaction scope, conflict handling and triggered effects after a load.
Why did an import overwrite the local staff note?
Restrict conflict updates to the columns the source is authorised to supply.
Why did an import report success after silently skipping a rejected row?
Record actual constraint failures before releasing the staged batch.
Why did the first row remain after the next insert failed?
Roll back the intended batch rather than treating statement ABORT as a whole-transaction rollback.
Why did one rejected line leave half an imported document?
Use a savepoint for the complete document family while preserving independent successful families.
Why did loading history create a new live notification row?
Make the supplied historical-load distinction part of the trigger’s actual condition.
Why did a one-row change counter miss two triggered writes?
Inspect each declared affected table beside the direct write count.
Why did verified rows vanish after the import rolled back?
Verify the committed state rather than only the writer’s uncommitted view.
Why does an import’s normalising trigger keep firing?
Guard the writeback using the supplied terminal value before the trigger’s recursive path.