Test that a Linux CSV and SQL export imports back with the same rows #3665

Problem

The Linux app exports CSV, JSON, Markdown, HTML, XML, Excel and SQL INSERT (linux/ROADMAP.md, Export), and imports CSV into an existing table up to 64 MiB (linux/ROADMAP.md, CSV import). The export side is tested on a 1,000,000-row table on six engines (linux/ROADMAP.md, release criterion 4), and CSV import has its own Docker tests (linux/crates/drivers/postgres/tests/integration/csv_import.rs). No test exports a table and reads the file back in, so a CSV writer and reader that disagree on quoting, NULL, line endings or encoding would pass both suites.

Proposed solution

• A Docker test per engine: export a table that holds the value corpus (linux/ROADMAP.md, release criterion 3) as CSV, import the file into an empty copy of the table, and compare the row count and a checksum of every row.
• Do the same for SQL INSERT by running the exported file in the editor against the empty copy.
• Run one case near the 64 MiB import limit.

Done when CSV and SQL INSERT round-trip on every engine in the Docker suite.

Alternatives considered

No response

Platform

Linux

Related database type

N/A / General