O it looks to me like the > 'exclusive' command just needs to be removed ... the threadsafe option that > sqlite3 was built with looks like it is internally handling the locking.
That would be my guess too. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
