On Jun 18, 2009, at 9:15 AM, Rizzuto, Raymond wrote: > I'm actually memory limited, which is why I am looking at moving > infrequently needed object to persistent store with sqlite3. I like > the idea of using the asynchronous i/o module so that the writing > can be done in a background thread, but still allow the main thread > to retrieve data that has been written or is in queue to be written.
You do not need the async I/O package for this. Simply set "PRAGMA synchronous=OFF" and it will behave as you desire (assuming your operating system implements a filesystem cache). > > > My main questions are about that module. I am a bit confused about > it since it is not distributed in the main amalgamations. I wanted > to make sure that I can just pull the 2 files from the source > tarball, or if there are other files I would also need. > > Additionally, since asynchronous i/o seems to sit apart from the > main sqlite3, I was wondering if it would be possible to use with an > older (3.5.9) version of sqlite3 that we already use in house. D. Richard Hipp d...@hwaci.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
