Timeline for Why is a comma a bad record separator/delimiter in CSV files?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2021 at 7:34 | history | edited | CommunityBot |
replaced https://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc
|
|
| Jul 27, 2017 at 7:58 | vote | accept | David Gasquez | ||
| May 23, 2017 at 12:39 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Nov 24, 2015 at 16:04 | comment | added | whuber♦ | @Voo +1 to your comment. However, anybody who is using CSV doesn't really care about bloated data files! | |
| Nov 23, 2015 at 13:22 | history | edited | Tim | CC BY-SA 3.0 |
added 1 character in body
|
| Nov 23, 2015 at 7:47 | history | edited | Tim | CC BY-SA 3.0 |
added 1087 characters in body
|
| Nov 22, 2015 at 20:10 | comment | added | Tim | @Voo Yes, but because "csv" files are used in such chaotic manner it is safer not to use commas and instead of them to use other separators, e.g. semicolons. This is the answer to OP question. There is nothing "better" in semicolons (or other non-commas) compared to commas, they are just simply safer choice in many cases. | |
| Nov 22, 2015 at 19:47 | comment | added | Voo |
Well any software implementing the actual CSV standard as defined by RFC 4180 would certainly know exactly how to interpret any given string. The argument that using , instead of a rarer separator bloats the data because you have to escape it all the time is true though. And obviously there's all those people who think they know how CSV works but really don't.
|
|
| Nov 22, 2015 at 11:45 | history | edited | Tim | CC BY-SA 3.0 |
added 233 characters in body
|
| Nov 22, 2015 at 11:39 | history | answered | Tim | CC BY-SA 3.0 |