3 ms·
They are exactly the same... Expect for the massive use case of storing human text, which contains tons of commas and zero ASCII separators. So if you decide n
by Dylan16807 2y ago
They are exactly the same... Expect for the massive use case of storing human text, which contains tons of commas and zero ASCII separators.
So if you decide not to support "strings", just "text", then those separators Just Work.
- qsort 2y agoIn that alternate universe nobody would have put them into some varchar column? The edge case still exists, which means that the standard would need to support it somehow, and we're back to exactly square one.
- Dylan16807 2y agoThe standard does not have to support nesting. But if I was writing a similar standard today and someone was pressuring me that I really had to make some kind of mechanism for nesting, I'd use something that transforms the field to remove the need for escaping, in a big and obvious way. Probably base64. That prevents most of the implementation issues you see with CSV.
- qsort 2y agoNeither does a trivial variation of CSV where quotes are not special and commas must be escaped in whatever way. The separator is completely immaterial, the resulting format is identical.
- Dylan16807 2y agoPeople screw up escaping. Don't escape. CSV needs escaping, so don't do CSV.