Build a useful investigation brief
Build boundary-specific text fixtures
Create values just below, at, and above the documented limit using ordinary text and a relevant multibyte representation. Include line breaks or normalized whitespace only if they matter to the field. Record expected acceptance and exact content independently, keeping character length separate from encoded byte size in the fixture description.
Trace measurements and transformations
Inspect the length measured before and after normalization, preview validation, domain validation, and destination assignment. Record each unit and rule. Locate where the first disagreement occurs, including any truncation applied before a later validator can see the original value and explain why content disappeared despite a successful import status.
Compare one aligned-boundary change
Evaluate the implicated rule change against the full boundary matrix and a normal short-value control. Check the error message and preserved source location for rejected values. Avoid silently trimming content to satisfy the destination; a valid correction should follow the declared field contract and keep unsupported text visible as a reviewable failure.
What to carry forward
Deliver the boundary matrix, measurement units, first inconsistent rule, and observed outcome of the bounded change. Separate visual clipping from stored text. A supported fix aligns the import’s promise with destination behavior and preserves accepted content, rather than merely moving a late error earlier without making its limit or location understandable.
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