Establish what is happening
Compare exact source and saved text
Choose a controlled value with a visible explanation of its leading, trailing, or internal whitespace. Compare the original field with preview and stored text, using a representation that makes spaces and line breaks distinguishable. A visually identical rendering can conceal different underlying strings or a value that was already trimmed.
Identify the field’s intended rule
Record whether the affected field permits trimming, preserves formatting, or relies on exact identity. Compare documented import behavior with the actual transformation. Keep whitespace handling separate from case folding and Unicode normalization, since several transformations can produce similar-looking results while changing different parts of the source value.
Check one affected comparison
Use the controlled value in a relevant lookup, display, or export and record the observable difference. Compare an ordinary unpadded control. If stored text is correct but a downstream comparison ignores or preserves spaces differently, retain that boundary instead of assuming the importer alone caused the mismatched behavior.
What to carry forward
End with exact before-and-after strings, the intended field rule, first transformation, and one demonstrated consequence. State any undecided whitespace semantics. The next owner should investigate a specific normalization or comparison boundary rather than applying a universal trim that may repair one field while damaging another.
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