Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

20
  • 20
    If you're just getting into the health domain and you think CSV is bad... just wait until you run into HL7! Commented Feb 14, 2011 at 21:46
  • 3
    @Greg LOL, don't frighten him, the surprise is always best :) Commented Feb 14, 2011 at 21:48
  • 47
    -1 This is an anti-CSV rant against problems not caused by CSV. What exactly do you think would happen if you read and wrote XML without a library? Your problems would be a hundred times worse. Commented Feb 14, 2011 at 21:52
  • 12
    "So why do we keep shafting each other? When will we stop?" I dunno, where I work we manage to use CSV just fine without anyone getting shafted (indeed - it's the XML stage that's by far more frustrating). Maybe you and your coworkers are doing something wrong? Commented Feb 14, 2011 at 21:56
  • 4
    All of the discussion so far misses a very real problem with CSV: the delimiter character is likely to appear in the data, and CSV takes a less-than-optimal approach to that issue (putting quotes around the data just pushes the problem downstream). A better approach would be to use pipe-delimited files. Commented Feb 14, 2011 at 22:59