Keep the lesson for the next incident
Document assignment meaning by operation
State what empty text, null markers, and omitted values mean for creation and updates. Identify any field-specific exception and explain the preview language users see. Keep the contract close to import guidance so an apparently cosmetic change to blank-cell display receives the right review.
Retain contrasting state examples
Keep fixtures that begin with a known existing value and end unchanged, cleared, or explicitly null under the supported rules. Include ordinary text and unknown markers. Record exact expected state so a later normalization change cannot pass merely because every result still looks visually blank in the interface.
Review new defaults and field types
Assign review when new imported fields, null conventions, or update modes are introduced. Check both the representation matrix and user-facing explanation. Track unintended clearing separately from generic invalid-value failures, because a silently accepted overwrite may otherwise disappear inside successful import statistics and remain hard to recognize.
What to carry forward
Close with a field-aware contract, representative state fixtures, and a named owner for changes to defaults or update semantics. Keep historical reconciliation separate. The next team should be able to predict an empty cell’s effect before running an import, rather than learning its meaning from the resulting state.
Technical background: PostgreSQL documentation.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow