Hi Marcus, I have no problem when the reading application gets a lock error because the writing application has a lock.
But the problem is the other way around: -> The writing application gets a lock error because someone reads! This is what I can't understand and what I didn't expect. I would expect that the writing application is undisturbed by any readers that open with SQLITE_OPEN_READONLY. Thanks Tino ------------------ Marcus Grimm wrote: > I'm afraid this is by design of sqlite: Sqlite will lock > the database during a writing transaction, I think no matter > if you open a 2nd connection using the readonly flag. > > the typical solutions are: > a) retry your read attempt after you receive a busy error code until > it proceeds. > b) consider shared cache mode and pragma read_uncommitted = True; > > hope this helps > > Marcus _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
