> Doesn't enabling WAL mode address the transaction size limit? Yes, you are right. WAL mode will eliminate transaction size issue, although there will be a WAL-file size issue. ;) But that issue is only about disk space, nothing related to locking of reading transactions.
Pavel On Fri, Jun 17, 2011 at 1:18 AM, Florian Weimer <f...@deneb.enyo.de> wrote: > * Pavel Ivanov: > >> To answer your original question: if you disable shared cache, start >> reading transaction on one connection and start writing transaction on >> the other connection then you'll be able to read on the first >> connection database in the state it was before writing transaction. >> But if your writing transaction will grow too big then it won't be >> able to proceed until reading transaction is finished. > > Doesn't enabling WAL mode address the transaction size limit? > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
