[
https://issues.apache.org/jira/browse/CSV-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877640#comment-13877640
]
Sebb commented on CSV-35:
-------------------------
I would be OK with adding an option to support this, but it should not be
called anything to do with MySQL.
It so happens that MySQL is known to generate the escape sequence, but other
CSV exports may do so as well, so I think the option name should relate only to
the functionality. The Javadoc can mention that the option may be needed for
MySQL parsing.
For example the option could be called: withEscapeCRLF(boolean).
Default should be false (i.e. only escape the CR).
> Escaped line separators are not supported
> -----------------------------------------
>
> Key: CSV-35
> URL: https://issues.apache.org/jira/browse/CSV-35
> Project: Commons CSV
> Issue Type: Bug
> Reporter: Emmanuel Bourg
> Fix For: 1.0
>
>
> Commons CSV doesn't handle escaped line separators, for example:
> {code}
> value1;value2;value3a\
> value3b
> {code}
> In this case the expected result is:
> {code}["value1", "value2", "value3a\nvalue3b"]{code}
> This kind of escaping is produced by MySQL, whether the field enclosing is
> enabled or not. It's possible to see enclosing quotes and escaped line
> separators like this:
> {code}
> "value1";"value2";"value3a\
> value3b"
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
