Darren Duncan wrote: > I don't have time to investigate right now, but both failing tests seem > to be connected with concurrent access to a table by two forked processes > (the test script forks a child, which does concurrent access). > > At least in the second case, the DROP TABLE and CREATE TABLE commands > are issued by the main process (after the child has dropped table2) and > are supposed to succeed, so I believe there's something else going on than > changed error codes (unless they trigger a bug within SQLite itself).
I assume you aren't sharing a single database connection object between the parent and child processes. That would violate one of SQLite's use assumptions and could definitely cause problems. Eric -- Eric A. Smith Money is the root of all wealth. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
