T wrote:
I can use a slightly modified CSV parsing handler, by just using this
as the row separator (instead of just plain linefeed):
");INSERT INTO VALUES("
Neat :)
Martin
-
To unsubscribe, send email to [EMAIL
On 10/26/06, T <[EMAIL PROTECTED]> wrote:
On 17/10/2006, at 9:31 PM, Martin Jenkins wrote:
> Does the SQL output work for your application? Might be just as
> easily parseable as yet-another-version-of-CSV...
I originally dismissed the sql "insert" output mode as most likely
having the same
Hi All,
On 18/10/2006, at 3:08 AM, Dennis Cote wrote:
You could try using the line mode output. It puts each field on a
line of its own, and separates each record with a completely blank
line. A sample is shown below.
sqlite> select * from t2;
a = 1
b = 2
a = 3
On 17/10/2006, at 9:31 PM, Martin Jenkins wrote:
Does the SQL output work for your application? Might be just as
easily parseable as yet-another-version-of-CSV...
I originally dismissed the sql "insert" output mode as most likely
having the same bug as csv. Upon checking, however, the
T wrote:
1. Is this a known bug in SQLite's csv output? Will it be fixed?
Tom,
Yes this is a know issue. I wouldn't hold my breath waiting for it to be
fixed
2. Is there another way to reliably get the contents of a database via
the command line? It must handle values containing pipes,
T wrote:
1. Is this a known bug in SQLite's csv output? Will it be fixed?
SQLite is a database library and the shell is just a handy tool that
happens to come with it. ISTM that the developers (should) give bugs
like this a pretty low priority.
2. Is there another way to reliably get the
Hi All,
In a similar vein to my previous posts about carriage returns in
values in a database, I now have an issue with quotes (ie: ")
It seems that the csv output from SQLite has a major problem/error.
Within CSV format, a quote should be returned as a double quote,
within quotes. For
7 matches
Mail list logo
