Charles Samuels <charles+sql...@cariden.com> wrote: > I need to be able to see the committed version of a database while a > new transaction is in the works. I would like to open the same > database file twice in a single thread, start a transaction on one of > the database connections, make a few writes to that database, then on > the other database connection do some reads on the other connection.
You may or may not be able to read on one connection while another is writing. It all depends on whether the changes fit into in-memory cache (in which case the writing transaction will hold RESERVED lock) or had to be spilled to disk (in which case it would hold EXCLUSIVE lock). The point when the lock is promoted is largely outside of your control. Though if the amount of data you plan to write is small, chances are high you'll be able to get away with this approach. Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
