BTW, beware of this thread http://www.mail-archive.com/[email protected]/msg50640.html too, although it wasn't understood what was the actual problem there.
Pavel On Tue, Apr 6, 2010 at 11:03 AM, Pavel Ivanov <[email protected]> wrote: >> Can anyone confirm whether concurrent >> access to an in-memory database is supported? > > No, SQLite doesn't support full concurrent access to any database. The > only concurrency you can earn is having on-disk database without > shared cache (so actually having several copies of the database in > memory). Of course I don't consider option of concurrency from > different processes. > > > Pavel > > On Tue, Apr 6, 2010 at 9:43 AM, Kent Boogaart <[email protected]> wrote: >> Hi there, >> >> I've recently been struggling with concurrency for an in-memory >> SQLite scenario. Basically, I want to be able to perform concurrent >> reads against an in-memory SQLite database, thus using multiple CPUs >> to good effect. >> >> I've tried everything I could think of and find in various blog posts >> to get this working, but SQLite insisted on synchronizing the reads. >> Switching from an in-memory DB to an on-disk DB immediately rectified >> the issue. >> >> What I'm wondering is whether SQLite flat out doesn't support >> concurrent access to an in-memory database, or perhaps whether I'm >> just doing something wrong. Can anyone confirm whether concurrent >> access to an in-memory database is supported? >> >> Thanks, >> Kent >> >> _______________________________________________ >> 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
