L.S.
Comma seperated files tend to become a bit too seperated when the field data
contains the character used for seperation while not being quoted ;)
Sqlite 3.5.4 uses shell.c::needsCsvQuote() to determine whether or not to
quote the field contents, but it doesn't check for the comma...... the
following patch changes that:
--- shell.c.orig 2007-11-30 02:28:11.000000000 +0100
+++ shell.c 2008-01-30 11:29:29.000000000 +0100
@@ -441,7 +441,7 @@
static const char needCsvQuote[] = {
1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1,
1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1,
- 1, 0, 1, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0,
+ 1, 0, 1, 0, 0, 0, 0, 1, 0, 0, 0, 0, 1, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
I understand a number of open tickets exist related to csv-behaviour, so the
above might be combined with those (the particular problem didn't seem to be
mentioned earlier, though).