On Thu, Sep 20, 2012 at 01:00:08PM +0000, Black, Michael (IS) wrote: > You weren't handling your forks correctly....
Maybe instead of turning my reduced example into a sequential program, you could have explained in what way my way of forking interferes with sqlite? In any case I believe that Richard Hipp has already fully answered my question. Thanks! He wrote: > On Debian Linux, I get back SQLITE_BUSY. > > The text error message for SQLITE_BUSY is (due to an historical accident) > "database is locked". Perhaps that is the point of confusion. So I was indeed misinterpreting "database is locked" as SQLITE_LOCKED. Maybe adding this note to the documentation would help others stumbling across a similar problem. Helmut _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
