sqlite-users, Here's my test environment:
-RHEL 5 on a vmware server (trying to move this to ESX) -C++ with 3 threads. One of them a write thread, one a main reader thread, and one a diagnostic reader thread -journal-mode=WAL -no change to default synchronization mode The write thread is updating a fairly small (< 1k) blob on one table. I can see the change on my diagnostic reader thread, but my main reader thread appears to be acting on an old copy. It has no application side caching, so would be doing a SELECT everytime it needs this data. It appears to have an old copy of this data until I restart the daemon Are there known consistency/timing issues with WAL? I'm wondering if vmware server's outdated disk support is causing any issues. More importantly, this is pretty hard to diagnose and catch. Are there any sqlite side logging or diagnostics I can enable that will help me prove where the bug lies (my code, sqlite, vm)? I have sqlite side logging enabled. I've played around with sqlite3_trace, but that only appears to log queries and not results. Thanks! --erik _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
