Data workflow
CSV workflows: preserve strings, join tables, compare keys and export SQL
CSV has fields, not a universal type system. Preserve original strings until an explicit receiving contract tells you which conversions are allowed.
Content updated: · Maintained by Hung Chi-Hsueh · corrections
Parse records, not physical lines
RFC 4180 allows commas and newlines inside quoted fields; a quote inside such a field is doubled. Splitting on commas or line breaks corrupts those records. Choose the input delimiter explicitly, or use first-record detection and review the detected separator; ties are rejected. UTF-8 files are decoded strictly; one initial UTF-8 BOM may be removed by the CSV parser.
With headers, the column editor rejects blank or duplicate names; headerless input instead receives numbered column names and can be exported without headers. Both modes reject rows with missing or extra fields and preserve string values, including 001, empty strings, spaces and quoted newlines. Single-column plain-text export preserves embedded newlines, which can make item boundaries ambiguous; use CSV or JSON when boundaries matter. Input is limited to 5 MiB, 20,000 data rows, 100,000 cells including headers and 200 columns. The first 100 rows are a preview; export contains the complete selected result.
Make transformations deliberate
Selecting, reordering and renaming columns changes the exported structure, not the original file. The filter offers case-sensitive equality, containment or skipping empty cells; whitespace-only cells are retained. Optional single-column deduplication keeps the first filtered row for each exact source value, including case and spaces, before sorting. Row sorting offers ordinal text or natural ordering, which uses browser Intl data and is not exact decimal arithmetic. Review row count, order and headers before downloading.
A primary-key comparison must identify rows uniquely. Use a composite key when one column is insufficient. Reordering records or columns should not create false data modifications; duplicate keys must be resolved before comparing. Empty key values can collide just like any other string.
Join enriches a table; diff compares revisions
For orders keyed by sku and products keyed by code, explicitly pair sku with code and append category. Left Join retains every main record in its original order; Inner Join keeps only matched records. Main keys may repeat. This tool deliberately requires unique lookup keys; it refuses first/last selection and many-to-many expansion. These are tool restrictions, not universal SQL rules.
Pair one to three key columns. Each component is an exact, case-sensitive string: 001 differs from 1, and spaces are preserved. A tuple containing an empty string is unmatched on the main side and rejected on the lookup side. Whitespace-only values are literal strings, not empty keys. Conflicting output column names must be renamed explicitly; main values are never overwritten.
Preview status distinguishes unmatched records from matched empty strings. CSV has no null type, so both export as empty fields; preview statuses and source record numbers are not appended. Export uses UTF-8, commas and CRLF without preserving original quoting or layout. Output is capped at 20,000 records, 100,000 cells including headers, 200 columns and 16 MiB. Copy is limited to 1 MiB; download retains the complete bounded output. The first 100 records and 1,000 characters per value are only a preview. Worker cancellation, source/settings changes and five-second timeouts invalidate old exports.
CSV and SQL have different safety boundaries
CSV quoting preserves field syntax, but does not neutralize spreadsheet formulas. A value starting with =, +, - or @ may be interpreted by spreadsheet software. These tools do not silently prefix or rewrite values; import untrusted data explicitly as text and follow your spreadsheet's security guidance.
PostgreSQL INSERT exports require explicit table and column identifiers, literal escaping and type choices. An empty CSV string is not automatically SQL NULL. Numeric identifiers can lose leading zeroes when converted, so keep them as text. A generated statement is not executed or a proof that the target database schema will accept it.
Local processing does not make an export anonymous or non-sensitive. Review data before sharing. Inputs are not uploaded, stored or placed in URLs; source edits invalidate previous export results.
id,note
001,"a,b"
002,"two
lines"
-- Preserve identifiers as text:
INSERT INTO "example" ("id") VALUES ('001');Data provenance