Hi All, I've been using sqlite to run my applications tests; it's small and light and all is well.
Lately I have been trying to improve the concurrency of these tests. The most obvious approach is to setup my in-memory database (using the ':memory:' location), then call fork() for each test. The sqlite docs warn against carrying a database through a fork call, but this appears to be because of how file locks work with fork (ie, irrelevant to :memory: databases). I gave it a try as described above (setup db, then fork) but the database appears to be completely empty. Anyone got any thoughts as to why this might be? - Daniel _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
