Check whether the outcome improved
Compare complete imported values
Import fixtures with one and several embedded newlines. Compare every field, the number of logical records, and the text surrounding each newline. Include a normal record immediately afterward; it helps reveal whether parser state leaks into the next row after a multiline value.
Exercise file and read boundaries
Repeat with a multiline field near the beginning, near a chunk boundary, and at the end of the file. Keep logical values identical across these cases. A result that depends on placement suggests the parser or preprocessing state is still sensitive to read boundaries.
Check malformed quote recovery
Try an unclosed quoted field in a controlled file. Inspect the error location and correction instructions, then retry a corrected copy. The importer should distinguish an invalid structure from an allowed embedded newline without silently dropping records or duplicating a previously accepted subset.
What to carry forward
Accept when valid multiline fields survive intact and malformed quoting produces a usable, correctly located failure. Record which newline conventions and chunk conditions were exercised. If only parsing was checked, leave the final import and user-facing error report as separate unfinished verification steps.
Technical background: DuckDB 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