[CSV-235] WRONG Implementation for RFC4180

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.6
• Component/s: Parser
• Assignee: Unassigned
• Reporter: Edward Xia
• Created: 12/Jan/19 00:30
• Updated: 16/Jun/19 12:46
• Resolved: 16/Jun/19 12:46

Description

https://tools.ietf.org/html/rfc4180#section-2
7. If double-quotes are used to enclose fields, then a double-quote
appearing inside a field must be escaped by preceding it with
another double quote. For example:

"aaa","b""bb","ccc"
Apparently, base on a previous issue: https://issues.apache.org/jira/browse/CSV-208, it turns out common-csv does not even support quote and escape to be the same character.

RFC 4180 defines that quote and escape are both DQUOTE, however in common-csv implementation, the default escape character is not DQUOTE, and it does not work if changed to DQUOTE.

This means common csv is not rfc4180 compliant.

Also, I'm puzzled by the fact that someone marked CSV-208 as fixed when nothing is fixed. Instead, it changed the behavior without documenting that the POSTGRESQL_CSV format does not even work out of the box with the default csv format that postgresql produces.