MS Access stores SQL as querydefs.
An internal more speedy format.
While the suggestion looks nice, i would go for a more binary version.
Something you could generate using some provided tool or generated (obtainable) by the library.

And not to focus on poor simplified SQL statements to increase speed.


----- Original Message ----- From: "Michael Scharf" <[EMAIL PROTECTED]>
To: <sqlite-users@sqlite.org>
Sent: Friday, November 25, 2005 4:49 PM
Subject: Re: [sqlite] Improve INSERT INTO tablename performance for bulk loads....


Eric Bohlman wrote:
Using prepared statements with placeholders would reduce the amount of parsing even further.

Well, I think
  INSERT INTO tablename VALUES (0,'foo') , (1,'bar') , (2,'baz');

is a kind of prepared statement, or it could be implemented as
a prepared statement. How would a prepared statemnt reduce the
amout of parsing significantly?

(1,2),  -- the overhead is 2 charactes per statement the '(' and
        -- the ')'

The data part of a prepared statement could drop the () but it
would need a separation character for columns ane one for rows.
You coul you use ',' and ';'.

The nice thing about the "row value constructors", is that it is
an (optional) part of SQL....

Michael



Reply via email to