Check whether the outcome improved
Exercise identity-sensitive strings
Import leading-zero identifiers, long values differing in their final digits, short controls, and mixed alphanumeric values. Compare character-for-character results. Include a fixture where later rows differ from the preview sample so the check covers type inference that may otherwise look correct at the beginning.
Check preview and explicit type selection
Confirm the preview preserves every digit and clearly shows the chosen field type. Where explicit text mapping exists, test that its selection reaches the importer. Reopen the saved record to establish that a correct preview was not followed by a later numeric conversion before persistence.
Verify relationships remain distinct
Exercise a controlled lookup or update using the exact imported identifier. Confirm similar strings remain distinct and the intended record is found. Do not weaken matching to ignore leading zeros as part of this check, because that would hide the preservation failure instead of proving the outcome.
What to carry forward
Accept when exact strings survive inference, mapping, storage, and the representative relationship check. Record any unsupported source format separately. Leave already damaged records outside this pass unless their identities have been reconciled independently; a successful new import does not prove historical references are repaired.
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