> Dropping the read lock is the same as rolling back the > transaction. The first process can, in fact, do this. And > the second process is waiting for the first process to do > this. But the first process cannot do it automatically. The > application must issue a "COMMIT" or "ROLLBACK" command > to make it happen.
This is looks little bit odd for me. For example, if 2 processes executes simple SQL INSERT commands and gets situation like above, one of them can easily drop read lock and wait for another one. There is no problem for this case. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
