The fastest performance you will get is with synchronous off. That will
relax the ACID requirement on the COMMIT but it can be unsafe if you get
a crash during the commit.
Mohd Radzi Ibrahim wrote:
Hi Rasanth,
I'm not an expert in SQLite. Not sure what kind of performance gain you
want to
Hi Rasanth,
I'm not an expert in SQLite. Not sure what kind of performance gain
you want to achieve. Perhaps you could try "pragma synchronous=off".
Or in-memory database...
I guess the journal is there to provide ACID db characteristic.
For me even with that out-of-the-box, the insert
Hi Radzi,
i do it with BEGIN and COMMIT. it is that, even in this case for transaction
support sqlite has to write into the journal files as well. i want to avoid
this too.
Thanks,
Rasanth
On Dec 26, 2007 11:34 AM, Mohd Radzi Ibrahim <[EMAIL PROTECTED]> wrote:
> On the contrary, sqlite work
On the contrary, sqlite work much-much faster when insert/update is
done within BEGIN and COMMIT;
regards,
Radzi.
On 26-Dec-2007, at 12:14 PM, Rasanth Akali Kandoth wrote:
Hi All,
I have an application which inserts large number of rows into a
table, where
transaction support is not
Hi All,
I have an application which inserts large number of rows into a table, where
transaction support is not necessary. For performance reason, i need to
disable the transaction support in sqlite version 3.3.17 . How can i do
it? any help is highly appreciated.
--
Thanks,
Rasanth
5 matches
Mail list logo
