> The major unexpected thing here is how SQLite deals with a case where > two different connections (which may be from different apps on > different computers) both have uncommitted changes. I think > explaining things using this as the key point may make explaining the > other aspects unnecessary: they will all come out in the wash.
Two connections are isolated from each other and cannot both have uncommitted writes. Unless you are using shared cache AND uncommitted read (which implies the same process running on a single machine) *or* WAL, you cannot "read" while you are writing, and only in the former case (shared cache AND read-uncommitted in a single process) can your "reader" see in process writes (originating from a connection using "the same" shared cache within a single process on a single machine). You need to re-read more slowly. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
