Anne,
To use a transaction just issue SQL to start it before you do your
inserts and SQl to issue a COMMIT when you finish. You can just use
sqlite3_exec to start and finish, no need for prepares.
Look up the documentation to get the transaction options which are
correct for your applicatio
Hi John
> Anne, you don't say that you make your 100 inserts a transaction.
Yes, I don't make the inserts in a transaction... because in that
moment don't know how to use it.
Now I have read in the Docu and after it seems to me, that I understand,
I insert a Test-Function in my App. I start it
Anne, you don't say that you make your 100 inserts a transaction.
Unless you do that the ACID feature of Sqlite will make it slow as it
has to finalize each insert onto disk before starting on the next.
Within a transaction it will do the 100 inserts then finalize the entire
100 onto disk in on
Anne,
Try wrapping your inserts in a transaction. Individual inserts are
quite fast, but transactions are not. Therefor anything that you can do
to reduce the number of transactions will boost the speed. My
preference is to wrap a transaction around every 200 or 300 inserts,
depending on t
Hi to all
Today I inserted as a Test 100 Records in my DB. I repeat therefor
100 times the same "Insert into...". The Job starts and I wait,
and wait, and wait.
I say, Programm hangs or died, because I do a Mistake in Code.
But it isn't.
The Job needs really so much time. Trace-Message shows
5 matches
Mail list logo
