No, SQLite doesn't do auto-commits every 25k insertions. It does auto-commit after each INSERT statement (no matter how many rows it inserts). If you wrap several INSERT statements into transaction it will execute faster.
Pavel On Sat, Jun 23, 2012 at 3:13 PM, Durga D <[email protected]> wrote: > Thank you(Pavel) for the prompt response. > > Sqlite does auto commit for every 25k insertions. Do I need to change the > number from 25k to x ( for ex: 100)? > > On Thu, Jun 21, 2012 at 7:54 AM, Pavel Ivanov <[email protected]> wrote: > >> On Wed, Jun 20, 2012 at 11:33 PM, Durga D <[email protected]> wrote: >> > Hi All, >> > >> > I have to develop a sqlite application. Within the process, multiple >> > threads are trying to access in write/read mode. Will sqlite supports >> read >> > and write at a time? >> > >> > scenario: 1. x number of records (x related data) are going to insert >> > in a transaction in ThreadA. still, not committed. >> > 2. In ThreadB (parallel thread), trying to read records >> > (x related data), which are there in transaction. >> > >> > By default, sqlite supports this scenario? or Do I need to enable any >> > flags/macros? >> >> Yes, SQLite supports that. You can see some "problems" only if ThreadA >> inserts a lot in one transaction, so that it doesn't fit into memory >> cache. >> >> >> Pavel >> _______________________________________________ >> sqlite-users mailing list >> [email protected] >> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users >> > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
