commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Gregory (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CSV-168) CsvFormat.nullString should not be escaped
Date Sun, 17 Jan 2016 19:40:39 GMT

    [ https://issues.apache.org/jira/browse/CSV-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15103888#comment-15103888
] 

Gary Gregory commented on CSV-168:
----------------------------------

I'm not sure about changing the behavior. What if you do want it escaped? I'm not sure there
is a case for that... What about adding a escapeNull boolean setting?

> CsvFormat.nullString should not be escaped
> ------------------------------------------
>
>                 Key: CSV-168
>                 URL: https://issues.apache.org/jira/browse/CSV-168
>             Project: Commons CSV
>          Issue Type: Bug
>          Components: Parser
>    Affects Versions: 1.2
>            Reporter: cornel creanga
>            Priority: Minor
>
> Hello,
> Use case: I'm generating MySQL dump files (text format) - for more details check this
- http://dev.mysql.com/doc/refman/5.7/en/select-into.html. 
> Issue: The value null is represented as "\N". Also by default the escape char is '\N'.
The CsvPrinter.printAndEscape method will convert this value into "\\N".
> I suggest to modify the CsvPrinter in order to not escape the nullString value  - it
should be written as it is. I can create a pull request if you want.
> I consider it a minor issue because it can be mitigated by making sure that the escape
character is not a part of the nullString - however in my case it means that the LOAD commands
should be modified accordingly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message