Fikirlər · 6 dəq oxu
When to use TSV instead of CSV for handoffs between teams
Choosing tab-separated values when prose columns or European decimals collide with comma delimiters, and interoperability tradeoffs with Excel and Unix tools.
Dərc 19 mart 2025 · Table
TSV uses tab characters between fields. It is a pragmatic choice when your data contains lots of commas (prose, addresses, JSON fragments) and you want to avoid heavy quoting. Unix pipelines and bioinformatics stacks often default to TSV for that reason.
When TSV wins
- Free-text columns where comma escaping would bloat the file.
- European numeric exports that use comma as the decimal separator alongside comma delimiters (confusing without strict locales).
- Quick handoffs between engineering tools that treat tabs as rare inside values.
Tradeoffs
- Tabs can hide inside pasted spreadsheet cells; always validate field counts.
- Some Windows workflows assume
.csveven when content is tabbed; document the delimiter for partners.
Table focuses on CSV interchange for the broadest business audience. If your pipeline emits TSV, convert to CSV at the boundary or use a one-line tool to swap delimiters before loading here.