There is no quick fix for something like this. You are welcome to fix this. Attention should also be paid to multiple user configurable field separators for varchar, longvarchar etc. which should still work after the changes.
Fred Toussi ----- Original Message ----- D. J. Hagberg wrote Sent: 04 September 2002 04:53 Subject: [Hsqldb-developers] Bug - Text tables and newlines in varchar columns It appears that the parser for text tables misses the possibility that varchar and longvarchar columns can contain LF, CRLF, or CR line breaks. ........... So I think this means 2 changes need to be made to Text table support: 1) If a varchar or longvarchar column contains a linebreak sequence, then it needs to get quoted on output. This duplicates Excel's behavior, I believe. 2) While the parser is looking for the end of the current row, it must ignore linebreak sequences inside a quoted column. Would anyone know how to fix this quickly? Or should I try to figure out how to fix this & submit a patch for (hopeful) inclusion in 1.7.1? -=- D. J. ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ hsqldb-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
