"Dennis Volodomanov" <dennis.volodoma...@conceiva.com> wrote in message news:8501919721c3de4c81bca22846b08721a3f...@lazarus.conceiva.com > Ok, thank you for confirming that. It seems that connection B > *sometimes* doesn't see data just inserted into a table by connection > A.
How do you know the read on connection B doesn't actually happen right _before_ the write on connection A? What kind of synchronization do you employ between these two threads? > Another question - is it possible for 2 threads sharing the same > connection to do an insert at exactly the same time, thus potentially > causing this problem? read_uncommitted just turns off read locks. Write operations still acquire write locks on tables they touch, so you can't have simultaneous inserts into the same table. > Maybe thread 1 did a "prepare", but not yet > "step" and the same data is being "prepared" by thread 2 This makes no sense. You don't prepare data - you prepare statements. No data is touched by sqlite3_prepare call. Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
