Check whether the outcome improved
Exercise each supported blank form
Test empty physical lines, whitespace-only lines, delimiter-only records, and quoted empty fields under the documented rules. Place them at the start, middle, and end. Include a quoted multiline field with a blank line so the check can detect a broad whitespace cleanup that changes legitimate text content.
Compare accepted and rejected identities
Inspect parsed and final record sets, not just summary counts. Confirm the distinctive valid records after blank inputs survive unchanged. Check that an intentionally invalid empty record receives the expected failure rather than being silently skipped merely because its fields happen to have no visible characters.
Verify correction references stay stable
Place a controlled validation failure after each blank structure and follow the reported row location. Confirm the source convention remains understandable after skipped inputs. Review the preview and final summary together so accepted, rejected, and ignored counts do not use incompatible definitions that leave users unable to reconcile the source file.
What to carry forward
Accept when each documented blank form follows its contract, real records and quoted content remain intact, and source references stay usable. Record unsupported forms separately. Keep verification open if only parser counts were checked; the resulting state and correction messages are independent parts of the import outcome.
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