On Wed, Nov 28, 2012 at 6:56 AM, Alejandro Martínez <[email protected]>wrote:
> Is that the only way? > > When i had done that in the past, the wal file grew constantly and i am > afraid it could fill the hard disk. > > That could happen if say... one of the reading processes doesn't > properly sqlite3_reset a prepared statement after stepping it. right? > Correct. The WAL file will grow until a checkpoint resets it. And a checkpoint cannot reset the WAL file while there is a pending transaction. So if you have a statement holding a transaction open, the WAL file will grow without bound. The solution there is to not hold read transactions open indefinitely. Call sqlite3_reset() when you are done with a statement so that its implied read transaction will close. > > Thank you for your quick answer. > > > > On Wed, Nov 28, 2012 at 9:52 AM, Richard Hipp <[email protected]> wrote: > > > PRAGMA journal_mode=WAL > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
