Check whether the outcome improved
Exercise the representation matrix
Import controlled empty fields, quoted empty strings, supported null markers, omitted values, and whitespace-only text. Record expected stored values for each supported field type. Include a nonempty control so the check can detect an overbroad conversion that changes ordinary text while repairing the original blank case.
Check update intent explicitly
Where updates are supported, begin with known existing values and exercise the documented unchanged and clearing cases. Compare actual saved state with those expectations. Confirm the preview explains the distinction before confirmation, especially where an empty-looking source representation is allowed to replace an existing destination value.
Inspect retrieval and filtering
Reopen the result and exercise a relevant filter or export that distinguishes null from empty text. Confirm that a display default does not conceal a stored difference. Record unsupported markers as rejected or literal values according to the contract, rather than silently interpreting unfamiliar text as a new null convention.
What to carry forward
Accept when parsing, preview, assignment, and retrieval preserve the declared meanings for the tested operations. Keep unresolved field semantics outside the pass. A successful creation case does not verify updates, and a visually blank result does not establish that the intended null or unchanged state was preserved.
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