You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 22, 2019. It is now read-only.
I'm using jackson to convert TSV piped output (from mysql command) to CSV. Right now I have to pick a character that will never happen to avoid the _nextQuotedString processing block , since this output is never quoted. If a cell starts with the quote char, it asplodes.
So I'd rather disable the quote char entirely. This is what I'm currently doing which for my input which effectively disables quoted cells.
This works, but is semantically inaccurate (I think?). Would it be possible to disable the quoteChar (and thus quoted cell values) altogether, to prevent any accidental interpretation of ANY character as starting a quoted value?
The text was updated successfully, but these errors were encountered:
I think this is an oversight: there is already withoutEscapeChar() method in CsvSchema, and I think there should then also be withoutQuoteChar() method. So I will take it as an RFE to do just that.
Since new features can only go in a minor version, this can go in 2.4.0.
In the meantime your approach should be valid, assuming that null byte (char 0) is never used -- and I don't think there are any legal use cases for textual content.
So I think you can use that until 2.4 is ready.
I'm using jackson to convert TSV piped output (from mysql command) to CSV. Right now I have to pick a character that will never happen to avoid the _nextQuotedString processing block , since this output is never quoted. If a cell starts with the quote char, it asplodes.
So I'd rather disable the quote char entirely. This is what I'm currently doing which for my input which effectively disables quoted cells.
This works, but is semantically inaccurate (I think?). Would it be possible to disable the quoteChar (and thus quoted cell values) altogether, to prevent any accidental interpretation of ANY character as starting a quoted value?
The text was updated successfully, but these errors were encountered: