<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_CLOSED bz_closed" title="CLOSED DUPLICATE - FILEOPEN Importing tsv/csv with no string delimiter causes whitespace only trailing column to corrupt" href="https://bugs.documentfoundation.org/show_bug.cgi?id=136013#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_CLOSED bz_closed" title="CLOSED DUPLICATE - FILEOPEN Importing tsv/csv with no string delimiter causes whitespace only trailing column to corrupt" href="https://bugs.documentfoundation.org/show_bug.cgi?id=136013">bug 136013</a> from <a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> Mike Kaganski</a> <pre>(In reply to Eike Rathke from <a href="show_bug.cgi?id=136013#c7">comment #7</a>) I enjoyed <a href="show_bug.cgi?id=136013#c6">comment 6</a> very much, made me recall playing with MySQL's "SELECT INTO OUTFILE" [1], where it puts even null bytes (and any other bytes that may appear in BLOBS), with configurable FIELDS ENCLOSED BY, LINES TERMINATED BY, and even absolutely inconsistent FIELDS ESCAPED BY, that needed a home-grown parser [2], because they obviously didn't know what xpusostomos knew ;) [1] <a href="https://dev.mysql.com/doc/refman/8.0/en/select-into.html">https://dev.mysql.com/doc/refman/8.0/en/select-into.html</a> [2] <a href="https://mikekaganski.wordpress.com/2021/02/18/reading-from-mysql-data-with-blobs-dumped-to-csv/">https://mikekaganski.wordpress.com/2021/02/18/reading-from-mysql-data-with-blobs-dumped-to-csv/</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>