News for hackers. Stuff that matters.
Re:CSV as a Data Source by zbanks on Thursday August 01, 2013 @04:47PM (#6143419)
Once your CSV (or TSV) files start having quoted fields, they become very tricky to parse using standard multi-purpose tools like sort, awk, & uniq.

It's hard enough when you have delimiters in quoted fields, but dealing with quoted newlines starts to become unreasonable, especially for line-based tools.

CSV files, as you say, are absolutely wonderful to create. Problems come up when you try to parse files other people write. Not everyone follows RFC 4180.

Re:CSV as a Data Source by jwilliams on Thursday August 01, 2013 @05:40PM (#6143727)
Problems come up when you try to parse files other people write. Not everyone follows RFC 4180.

Plus you've got encodings. If you're accepting CSVs from users, they'll generally come from Excel, which will produce different encoding in different circumstances.

Re:CSV as a Data Source by guard-of-terra on Thursday August 01, 2013 @05:11PM (#6143567)
With tab separated values this is not a big problem in practice. On the other hand, you can sort tsv, but you can't sort quoted csv.
Re:CSV as a Data Source by sopooneo on Thursday August 01, 2013 @09:14PM (#6144804)
Why not? I ask in earnest.
Re:CSV as a Data Source by guard-of-terra on Friday August 02, 2013 @02:35AM (#6145617)
sort -n gets confused by quotes.