Hello Thomas,
you are right in principle: The gain should be not too great. However,
the number of calls to sqlite3_bind_text is * of columns>, which is *very* high.
Also, i suspect that sqlite3_bind_text makes a copy of the text i pass,
which could be eliminated too. Or am i wrong there?
> However, I would very much like a "bulk insert" - call to
> sqlite (Oracle
> OCI does this, for example), where i can put many (thousands)
> of records
> into the database with one call. Is there any chance of
> something like
> this ever to be added to sqlite?
I can't speak
On 9/14/05, Rajan, Vivek K <[EMAIL PROTECTED]> wrote:
>
>
> I am wondering if there techniques/tricks which can improve the total
> insertion speed of my application. Any suggestions/feedback?
>
Remove indexes from the tables you're inserting into.
If you need that data for queries later you
Hello
You can also speed up the inserts when creating the index after the
inserts. To check the constraints you could use QDBM
(http://qdbm.sourceforge.net/).
Rajan, Vivek K wrote:
Hello-
In my application, I perform large number of insertions (~100K) to
create a SQLite database. The
Hello Vivek,
I have a very similar application, without the foreign key constraints,
however.
If you use sqlite3_prepare() once for your statement, then
sqlite3_bind_...() with every call, and if you wrap all the inserts int
one transaction (seems that you do), your speed schould be optimal.
5 matches
Mail list logo
